Allow merges if pr.mergeable_state == 'has_hooks' #37
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
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.
This change allows merges to proceed even if the mergeable_state is reported as 'has_hooks'.
In GitHub Enterprise, global pre-receive hooks can be defined that can disallow pushes. When such hooks are defined, the github api will report the mergeable_state as 'has_hooks' instead of 'clean'. The meaning of this is "You can push this merge, but the pre-receive hook may disallow it". Tutter should allow this state in the same way as a 'clean' state.