Right now, the all-contributors bot is deployed using Vercel. I see the "approve" deploy button on PRs, but I don't see how to test that things are working, and I don't see that I have access to the Vercel team.
@gerteck mentioned this related to #516 and @JoshuaKGoldberg has some understanding of apps. But without access to the Vercel team, it's hard to understand what Vercel is doing. It's also hard to determine how to test whether updates to the CLI will affect how the bot operates.
My fear is updating the CLI and publishing to npm (we are close there), then updating the bot, and things breaking, and it becoming hard to fix.
I emailed the NPM team about access to NPM and Vercel. They gave us access to NPM, but no one on that team was aware of Vercel or the bot. So the bot must be a newer feature. (newer as in newer than 2020 when that team was active ) 🙃
@gr2m I think you are a super busy human, BUT if you happen to see this and have any thoughts on how we can better understand (and test) deployment of the app here as we update the cli, that would be wonderful. cc @Berkmann18 @JimMadge
This issue is why work has slowed down here in this repo, but we are cruising along in the cli repo towards a fresh npm release ❇️ so project work IS moving forward!!
Right now, the all-contributors bot is deployed using Vercel. I see the "approve" deploy button on PRs, but I don't see how to test that things are working, and I don't see that I have access to the Vercel team.
@gerteck mentioned this related to #516 and @JoshuaKGoldberg has some understanding of apps. But without access to the Vercel team, it's hard to understand what Vercel is doing. It's also hard to determine how to test whether updates to the CLI will affect how the bot operates.
My fear is updating the CLI and publishing to npm (we are close there), then updating the bot, and things breaking, and it becoming hard to fix.
I emailed the NPM team about access to NPM and Vercel. They gave us access to NPM, but no one on that team was aware of Vercel or the bot. So the bot must be a newer feature. (newer as in newer than 2020 when that team was active ) 🙃
@gr2m I think you are a super busy human, BUT if you happen to see this and have any thoughts on how we can better understand (and test) deployment of the app here as we update the cli, that would be wonderful. cc @Berkmann18 @JimMadge
This issue is why work has slowed down here in this repo, but we are cruising along in the cli repo towards a fresh npm release ❇️ so project work IS moving forward!!