fix(ci): approve checks after Dependabot lock repair - #137
Merged
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
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.
Summary
pull_requestworkflow GitHub creates inaction_requiredfor the repaired commitmain(EF Core) anddapperwithout merging the branchesWhy
GitHub creates
pull_request/synchronizeworkflows triggered by aGITHUB_TOKENupdate in an approval-required state. PRs #132 and #133 demonstrate the failure: the lock files were repaired, but all checks on the repaired commit have zero jobs and conclusionaction_required. The existing fallback manually dispatches only a subset of checks, omitting checks such as dependency review and script syntax.Validation
git diff --checkmainNo application implementation changes are included.