I've renamed the master branch to be called main in-keeping with updates across the org.
In your local envs you can switch the upstream by:
git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a
before making any changes. But most of you shouldn't be making changes to the main branch anyway :P
This should have minimal impact on regular users, and only the admins will have to amend some things when we do the next release.
If you have any questions or need help with this move comment here or give me an email on carley.martin@usask.ca
Thanks,
Carley
Note that the new default branch is also develop, this means that any new PR made will automatically assume it wants to be merged into develop not main which is the general workflow anyway.
Hi all,
I've renamed the master branch to be called main in-keeping with updates across the org. In your local envs you can switch the upstream by:
before making any changes. But most of you shouldn't be making changes to the main branch anyway :P This should have minimal impact on regular users, and only the admins will have to amend some things when we do the next release.
If you have any questions or need help with this move comment here or give me an email on carley.martin@usask.ca
Thanks, Carley
Note that the new default branch is also develop, this means that any new PR made will automatically assume it wants to be merged into develop not main which is the general workflow anyway.