-
Notifications
You must be signed in to change notification settings - Fork 371
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
Enable gh/ci on maint-3.0 #6707
Conversation
branches: [ master ] | ||
branches: | ||
- master | ||
- maint-3.0 |
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.
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.
Sounds good. Quick clarification: do we usually update maint branches via PRs or manually merging fixes and pushing directly to maint? If the former, all good. Otherwise we may want to change the trigger for maint to a push.
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.
I think we intend to only allow PRs in general, but @rljacob can confirm
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.
Yes PRs and the PR issuer has to make sure to change the target to a maint branch.
Activate gh/ci workflows on maint-3.0.
[BFB]