Remove mergify from repository #11
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
While it initially seemed handy, the danger of automatically merging a broken PR is too great in this specific project. This is because the cirrus-ci_retrospective action must necessarily execute after cirrus-ci is finished. Due to limitations of the github issue-labling system/permissions, it is likely mergify could merge before the self-test run of cirrus-ci_retrospective on a PR has completed. Signed-off-by: Chris Evich <cevich@redhat.com>
|
Successfully ran test cirrus-ci_retrospective from this PR's f22a7a9aa205cf024b96f91d2576584410dc0294 Results and artifacts are now available. |
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.
While it initially seemed handy, the danger of automatically merging a
broken PR is too great in this specific project. This is because the
cirrus-ci_retrospective action must necessarily execute after cirrus-ci
is finished. Due to limitations of the github issue-labling
system/permissions, it is likely mergify could merge before the
self-test run of cirrus-ci_retrospective on a PR has completed.
Signed-off-by: Chris Evich cevich@redhat.com