-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
CI/DOC: replace master -> main branch #45336
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
CI/DOC: replace master -> main branch #45336
Conversation
This has failed a few times it appears. Not sure why this PR would influence this failure: |
do we need to backport this? (yes?) |
I would think so. |
thanks @jorisvandenbossche |
@meeseeksdev backport 1.4.x |
Something went wrong ... Please have a look at my logs. |
Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
The backport is actually already done at #45338 by meeseeksdev (not fully sure why he mentioned here that "something went wrong") |
because @jreback triggered manually. The bot sometimes does not pick it up (although not noticed this lately) |
yeah i always trigger (though i realiE i don't really need to) |
yeah probably safer to make sure nothing gets missed. If the PR has a release note then I check release notes are in sync so these won't get missed. If if fixes ci then again won't get missed as the ci would be failing on the backport branch. If it's a doc fix or some other cleanup then could potentially be missed if the bot does not pick it up and it is not triggered manually. |
Follow-up on #39577