-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Renaming master branch to main on Monday, July 6th #605
Comments
@marbud0 @marceloleitner @martinm82 @matbu @mator @mattclay @maxamillion @mbrancato @mdavranche @meerkampdvv @mhumeSF @michalmiddleton @millerjeffrey @montag451 @moonrail @moreati @mumblemaker @musikov @nasirhm @nejch @networkers-pl @nitzmahone @notok @odyssey4me @olof @pabelanger @panyy3 @particledecay @paulfariello @pengzhimou @pertoft @PetzJohannes @phumpal @pklejch @pranavk45 @precurse @pshirshov @ptzianos @quidame @raspbeguy @relrod @resmo @RGM-OSC @riemers @rosowiecki @ruheenaansari34 @russoz @s-hertel @saito-hideki @samcarpentier (you all forked this repository or are otherwise related to it) |
@samccann @samdoran @sbulage @serverfriendsorg @Shaps @SiebeVE @simonbaird @sivel @smeeus @ssbarnea @ssteve-dev @tabacha @tblakex01 @tchernomax @theque5t @thinkdoggie @Thulium-Drake @tiggi @timway @tomaszkiewicz @Tomorrow9 @traittinen @trammel @trumbaut @turntabl @bill-n @effaamponsah @FrancisBilla @gitter-badger @twmartin @Tyler-2 @unai-i @varesa @vbotka @vcc-caeit @Veltarn @vlours @WojciechowskiPiotr @wojtek0806 @wrcomb @xek @xiangge @ximon18 @xlab-si @xoxys @yanzhangi @ylmrx (you all forked this repository or are otherwise related to it) |
bot_skip |
Thanks for notifying @felixfontein |
@nasirhm you're welcome! I'm going to lock this, since quite many people are CCed here and I want to avoid unnecessary spam. If you have questions, either contact us via IRC (Freenode, #ansible-community) or create a new issue. (If there is a new issue I'll link it here so that other interested people can look there.) I hope you all agree that this is better :) |
I'm starting now with the rename... |
Mostly done. The old |
The |
I'm closing this now. Please don't forget to update your forks, and at least get the |
Renaming
master
branch tomain
on Monday, July 6thThe Ansible team decided to rename the
master
branch in all Ansible-controlled collections tomain
(see ansible-collections/overview#83 and ansible-collections/overview#87 for history and more information). We plan to apply this change to thecommunity.general
repository on Monday, July 6th, in the morning (Europe), i.e. before the Contributor Summit.If you have created a pull request, there is nothing you need to do - we will retarget the pull requests so they will get merged to
master
and not tomain
.If you have forked the repository, and wish to keep the fork, we recommend that you also update your fork to use
main
as the default branch. See https://github.com/ansible/community/wiki/Changing-the-git-default-branch-to-main#updating-a-fork-on-github and https://github.com/ansible/community/wiki/Changing-the-git-default-branch-to-main#update-the-repository-on-github for details on how to do that.To update your local clones, see https://github.com/ansible/community/wiki/Changing-the-git-default-branch-to-main#updating-local-clones for instructions on how to adjust them to using
main
instead ofmaster
.If you have questions, please reach out to us on #ansible-community (Freenode).
CC @abadger @achauvinhameau @AdamGoldsmith @Akasurde @akiselev1 @AlanCoding @alxgu @amigus @aminvakil @amleshkov @Andersson007 @andreaso @andytom @anshulbehl @apollo13 @asciifaceman @AshishVarshneyy @autogun @axarriola @bandit145 @bcoca @bergmannf @BerkhanBerkdemir @bidord @billdodd @bmillemathias @bmillemathias-1a @BondAnthony @briantist @C0rn3j @CameronNemo @cassio-santos @chiehmin @chris1911 @crashwind @cspeidel @cusux @CWollinger @D3DeFi @danowar2k @das7pad @decentral1se @devfaz @dpassante @dsg22 @dudefellah @emonty @eryx12o45 @fcastello @fgiorgetti (you all forked this repository or are otherwise related to it)
bot_skip
The text was updated successfully, but these errors were encountered: