ci: run commitlint once per same-repo PR#4795
Merged
Merged
Conversation
Scope the push trigger to the default branch so Renovate (and any other same-repo branch) fires only the pull_request event instead of both push and pull_request, which currently runs the Commitlint check twice for a single PR. Coverage improves rather than regresses: the pull_request path validates the full commit range (--from base --to head), whereas the dropped push run only checked --last (the tip commit). Direct pushes/merges to master still run the --last validation, and fork PRs were already single-run. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
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
1 participant
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.
Scope the push trigger to the default branch so Renovate (and any other same-repo branch) fires only the pull_request event instead of both push and pull_request, which currently runs the Commitlint check twice for a single PR.
Coverage improves rather than regresses: the pull_request path validates the full commit range (--from base --to head), whereas the dropped push run only checked --last (the tip commit). Direct pushes/merges to master still run the --last validation, and fork PRs were already single-run.