Replies: 1 comment 3 replies
-
Hi @nixpanic! This is intentional. For now, Mergify completely ignores any pull request that touches its configuration file. We agree that we should probably remove some of the limitations and keep the check on the merge/queue actions. I added this to our backlog. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
When Mergify detects changes to
.mergify.yml
it will not merge PRs automatically, but maintainers of the repository need to do this.Unfortunately, it also seems that labels are not set on the PR where
.mergify.yml
is modified. This does not seem like a critical operation that depends on the maintainer of the repository. I wonder if this is intentional, or if it can be changed in the future.Beta Was this translation helpful? Give feedback.
All reactions