docs: document the production deploy path - #22
Closed
damartinezjulio wants to merge 2 commits into
Closed
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
The branch ruleset requires a status check named 'lint', but the job was named 'build', so that check never existed and 'main' could never be created.
Contributor
Author
|
Superseded — |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
@Sigilix ignore
@coderabbitai ignore
Documents that
mainis the production branch and how to force a prod deploy — after discovering docs.sigilix.ai had been serving a stale pinned deployment while every merge only produced Preview builds.This PR also runs
lintso the commit is green, which is required beforemaincan be created under the repo ruleset.