ci(repo-ci): scan the full push range for attribution residue#30
Merged
Conversation
On pull_request the check scans origin/<base>..HEAD. On push, github.base_ref is empty, so AI_RESIDUE_BASE_REF resolved to a bogus ref and the check fell back to scanning only the single HEAD commit — narrower than intended and prone to false positives on a HEAD whose body merely mentions a marker word. Use github.event.before..HEAD on push so every pushed commit is scanned and commits already on the base branch are not re-scanned. Matching logic is unchanged.
NWarila
added a commit
that referenced
this pull request
Jun 5, 2026
On `pull_request` the attribution-residue step scans `origin/<base>..HEAD`. On `push`, `github.base_ref` is empty, so `AI_RESIDUE_BASE_REF` resolved to a bogus ref and the checker fell back to scanning only the single HEAD commit. This widens push-event coverage to `github.event.before..HEAD` (every commit in the push) and stops re-scanning commits already on the base branch. The marker-matching logic is unchanged — this only fixes the commit range on push events. Resolves the spurious failure on the latest `main` run.
NWarila
added a commit
that referenced
this pull request
Jun 6, 2026
On `pull_request` the attribution-residue step scans `origin/<base>..HEAD`. On `push`, `github.base_ref` is empty, so `AI_RESIDUE_BASE_REF` resolved to a bogus ref and the checker fell back to scanning only the single HEAD commit. This widens push-event coverage to `github.event.before..HEAD` (every commit in the push) and stops re-scanning commits already on the base branch. The marker-matching logic is unchanged — this only fixes the commit range on push events. Resolves the spurious failure on the latest `main` run.
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.
On
pull_requestthe attribution-residue step scansorigin/<base>..HEAD. Onpush,github.base_refis empty, soAI_RESIDUE_BASE_REFresolved to a bogus ref and the checker fell back to scanning only the single HEAD commit.This widens push-event coverage to
github.event.before..HEAD(every commit in the push) and stops re-scanning commits already on the base branch. The marker-matching logic is unchanged — this only fixes the commit range on push events. Resolves the spurious failure on the latestmainrun.