Remove mergify from action #3882
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Chris Lalancette <clalancette@gmail.com>
clalancette
added
the
backport-all
clalancette
approved these changes
Sep 15, 2023
mergify bot
pushed a commit
that referenced
this pull request
Sep 15, 2023
* GitHub trigger updated for just pull requests Co-authored-by: Chris Lalancette <clalancette@gmail.com> (cherry picked from commit 3057500)
mergify bot
pushed a commit
that referenced
this pull request
Sep 15, 2023
* GitHub trigger updated for just pull requests Co-authored-by: Chris Lalancette <clalancette@gmail.com> (cherry picked from commit 3057500)
clalancette
pushed a commit
that referenced
this pull request
Sep 15, 2023
clalancette
pushed a commit
that referenced
this pull request
Sep 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have made several contributions and have noticed that
Mergifygenerates a new pull request for each backport branch. This leads to the GitHub action being triggered 8 times for every accepted pull request.Due to this issue, I suggest excluding the check from the triggers for branches that begin with
mergify/bp/. By doing so, we can prevent 4 unnecessary executions (2 from Iron and 2 from Humble).It would be beneficial to also implement a feature that disables triggering upon each branch merge.