fix: verify if PR was manually merged with auto-merge config #422
Conversation
This file contains hidden or 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
motatoes
requested changes
Jun 30, 2023
Co-authored-by: Mohamed Habib <moe.habib9@gmail.com>
motatoes
approved these changes
Jun 30, 2023
ben-of-codecraft
pushed a commit
to ben-of-codecraft/digger
that referenced
this pull request
May 21, 2024
…q#422) * fix: verify if manually merged with auto-merge config --------- Co-authored-by: Mohamed Habib <moe.habib9@gmail.com>
breardon2011
pushed a commit
that referenced
this pull request
Sep 17, 2025
* fix: verify if manually merged with auto-merge config --------- Co-authored-by: Mohamed Habib <moe.habib9@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Relates to #399
Complement to fix made in #401
Fixing the use case when manually merging a PR with the following digger.yml config:
on_commit_to_default: [digger apply]Digger would run the
applycmd and then verify if the PR is mergeable (for the auto-merge config), which would result in a failure.