Librsvg's development branch is now called main
source link: https://people.gnome.org/~federico/blog/librsvg-main-branch.html
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Librsvg's development branch is now called mainFederico
→ Blog
→ Librsvg's development branch is now called main Open navigation
I have just renamed librsvg's master branch to main, as other
modules already have.
This is what I did:
- Rename the local branch, and push it:
git branch -m master main
git push origin main
-
Change the default branch in gitlab; for librsvg this is in the repository settings / Default branch - change that to
main. -
Set the same protection for the
mainbranch as there was formaster, if any - repository settings / Protected branches -> create a new protection and copy the settings frommaster. -
Unprotect the
masterbranch so I can delete it - repository settings / Protected branches -> unprotect themasterbranch. -
Delete the
masterbranch in the branches list. -
Update the CI and build scripts: for librsvg it was just
.gitlab-ci.yml. -
Update your documentation: for librsvg it was just
COMPILING.md. -
Notify the release team; I created an issue and one for gnome-build-meta.
If you have a local checkout, you can do this:
# update from upstream
git fetch origin
# switch to your local master branch
git checkout master
# rename your local branch
git branch -m master main
# Remove the old upstream...
git branch --unset-upstream
# ... and set the new one
git branch -u origin/main
That's all!
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK