ci: github actions to deploy to vercel #212
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@matteobad is attempting to deploy a commit to the Salgsmaskin Team on Vercel. A member of the Team first needs to authorize it. |
|
Trying to merge it now @matteobad |
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
As of right now, @meglerhagen is the only one who can trigger a deployment on Vercel and the only one with access to it. Rightfully so since it's his account, but this is slowing us down in approving, testing, and merging PRs.
With this PR I've added two new GitHub Actions:
The idea is to trigger deployment from GA so that @meglerhagen's Vercel account remains private, but we can make CICD faster and with fewer manual steps.
What type of PR is this? (check all applicable)
Steps to QA
Added to documentation?
[optional] Are there any post-deployment tasks we need to perform?
These ENV need to be added to GitHub secrets and are required for the new Actions to work:
Notes