-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Prepare to rename master to main #3420
Prepare to rename master to main #3420
Conversation
Signed-off-by: Juraci Paixão Kröhling <[email protected]>
Codecov Report
@@ Coverage Diff @@
## master #3420 +/- ##
==========================================
- Coverage 96.50% 96.48% -0.03%
==========================================
Files 261 261
Lines 15267 15267
==========================================
- Hits 14734 14730 -4
- Misses 451 454 +3
- Partials 82 83 +1
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Similar question to the other repos. Is there a reason to keep functionality for both master and main? Is that just something we want during a transition period?
Once we switch completely to main, I'll send another PR removing master from the CI files. |
Signed-off-by: Juraci Paixão Kröhling <[email protected]>
There are a lot of references to |
GitHub sets a redirect, we should be fine for the old ones. For the new ones, we should use the new branch name. Although it wouldn't be hard to rename it as part of this PR... |
Signed-off-by: Juraci Paixão Kröhling <[email protected]>
Changelog changed. |
Signed-off-by: Juraci Paixão Kröhling [email protected]