You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
main is becoming the new default (already has on GitHub), and now seems like a good time, since we're already de-forking and revisiting our branching workflow.
I've already pushed a main branch at the master commit, so if we want to be cautious with this, we could
switch the "default branch" on GitHub (for cloning & PRs) to main
manually fast-forward master to meet main as PRs merge
slowly update production references from master to main
delete master when it feels safe
without needing to update all production references from master to main right away.
The text was updated successfully, but these errors were encountered:
main
is becoming the new default (already has on GitHub), and now seems like a good time, since we're already de-forking and revisiting our branching workflow.I've already pushed a
main
branch at themaster
commit, so if we want to be cautious with this, we couldmain
master
to meetmain
as PRs mergemaster
tomain
master
when it feels safewithout needing to update all production references from
master
tomain
right away.The text was updated successfully, but these errors were encountered: