[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[sc-dev] Notice: Upcoming changes to branch naming across SC org
Hey all,
Another message will follow this one once the change is complete, at which point action will be needed on your part.
If you have forked any of these repositories on GitHub, after April 17 you will be able to update by performing the same renaming operation on your own repository via the GitHub UI: go to your repo, click "branches", click the pencil icon next to the "master" branch to rename, and set the name to "main".
If you have cloned any of these repositories locally, after April 17 you will be able to follow these steps to update your branch. Note that the GitHub UI also shows a reminder with similar instructions.
# "move" master to main
git branch -m master main
# set the correct upstream -- this will work regardless of whether you had the
# SuperCollider remote named as "upstream" or "origin"
git branch -u $(git config branch.main.remote)/main main
# update your local reference for the SuperCollider remote
git remote set-head $(git config branch.main.remote) -a
This has no impact on repositories which are git submodules under ordinary usage. You will need to repeat the steps for updating a local clone if you are developing a submodule locally.
Regards,
Brian
------------
composer, programmer
brianlheim.com
github.com/brianlheim
pronouns: they/them