Update README to reflect making main the default branch #848
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
NOTE: this pull request branch is against the |
|
Probably need to add something to the README about our plan for keeping the |
rgommers
approved these changes
Jun 17, 2024
There was a problem hiding this comment.
These changes and the new blog post process looks great to me, thanks Gabriel!
I won't merge this now, since it'd be good for at least one of @trallard or @pavithraes to also have a look.
trallard
approved these changes
Jun 18, 2024
|
Great! I just changed the default branch in the repo settings to |
|
Thanks! I went through the updates as well, and all looks good. :) |
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.
This PR updates the README to reflect the discussion on a recent release PR (copy-pasted below).
I also reworded some things and moved two sections to the top:
Once it is approved, right after merging it, I will change the setting in GitHub to make
mainthe default branch.Link: updated README
As for getting rid of the two-stage deploy process, here are some thoughts:
mainto be the default branch so that blog authors branch off main when working on a blog postdevelopbranch in place for riskier changes to the repo that should go through the two-stage deploy processdevelopbranch withmain. Seems to me thatmainshould be the source of truth anddevelopshould mirrormain. (The alternative would be merge commits from main to the develop branch but that sounds messy in the long run.)