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
In keeping with the latest repository convention (and thanks to a recently-added ability to rename the branch easily), we can sync up our repo to the newest convention where master is called main
The text was updated successfully, but these errors were encountered:
The master branch was renamed to main during the 1/29 meeting, and most of the team was able to perform the local commands successfully. @Amelie1253 discovered that something was off on her local clone (detached head) and was unable to do the commands; @MilkaZek was not available. So for reference, here are the commands to perform:
git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a
@Amelie1253 will seek to clone a fresh copy and transfer existing work, plus monitor if the problem reoccurs
In keeping with the latest repository convention (and thanks to a recently-added ability to rename the branch easily), we can sync up our repo to the newest convention where
master
is calledmain
The text was updated successfully, but these errors were encountered: