-
Notifications
You must be signed in to change notification settings - Fork 155
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
mergify: update rules #6706
mergify: update rules #6706
Conversation
@@ -61,16 +61,14 @@ pull_request_rules: | |||
- merged | |||
- closed | |||
- and: | |||
- label=automation | |||
- head~=^update-go-version | |||
- head~=^updatecli.* |
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.
See #6700
- name: delete upstream branch for mergify backports | ||
conditions: | ||
- or: | ||
- merged | ||
- closed | ||
- and: | ||
- head~=^mergify/bp/.* | ||
actions: | ||
delete_head_branch: |
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.
We want to delete any branches coming from PRs always after they are merged or closed
- name: delete upstream branch with changes on ^.mergify.yml that has been merged or closed | ||
conditions: | ||
- or: | ||
- merged | ||
- closed | ||
- and: | ||
- label=automation |
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.
this label is not something used anymore, apparently -> #6645
|
What does this PR do?
Update mergify rules to use the Buildkite checks and remove the automation labels and update some other bits and pieces
Why is it important?
This should help with:
Checklist
./changelog/fragments
using the changelog toolDisruptive User Impact
How to test this PR locally
Related issues
Questions to ask yourself