refactor(tooling-ci): connect vercel to git #4766
Open
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
begonaalvarezd
requested review from
msarcev,
alexsporn,
thibault-martinez,
DaughterOfMars and
Dr-Electron
as code owners
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 4 Skipped Deployments
|
…y manual production Co-authored-by: JCNoguera <[email protected]>
6 tasks
…production Co-authored-by: JCNoguera <[email protected]>
begonaalvarezd
changed the title
DaughterOfMars
approved these changes
Jan 14, 2025
begonaalvarezd
commented
Jan 14, 2025
There was a problem hiding this comment.
I would create 2 of these so I can use them in all projects @VmMad
- One with preview only
- One for all environments
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 of change
Close #4417
Links to any relevant issues
Be sure to reference any related issues by adding
fixes #(issue).Type of change
Choose a type of change, and delete any options that are not relevant.
How the change has been tested
Describe the tests that you ran to verify your changes.
Make sure to provide instructions for the maintainer as well as any relevant configurations.
Change checklist
Tick the boxes that are relevant to your changes, and delete any items that are not.