-
Notifications
You must be signed in to change notification settings - Fork 3k
Mergify update #12673
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 #12673
Conversation
1. If a PR is closed but not merged then remove all labels 2. If a release version is added and there are release version missing or Release review required, then remove those labels 3. In the check for conflicts rule, add the condition 'open' so that it isn't applied to closed or merged PRs
@adbridge, thank you for your changes. |
.mergify.yml
Outdated
- name: release version is a must for merged PRs part 2 | ||
conditions: | ||
- merged | ||
- -label=^(release-version) |
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 shouldn't be - label=^(release-version)
- otherwise its negative (not release label and merged) ?
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.
Ah yes it should be
Pr is merged and a label beginning with 'release-version' is present. I missed the extra '-'
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.
Should now be fixed
@adbridge, thank you for your changes. |
CI started |
Summary of changes
A number of Mergify rules were not quite working as expected. This update fixes them and adds a new rule.
Impact of changes
Mergify rules work correctly
Migration actions required
Documentation
None
Pull request type
Test results
Reviewers