Scope O2 linter push runs to pushed commit range - #1
Draft
annetkonings with Copilot wants to merge 2 commits into
Draft
Scope O2 linter push runs to pushed commit range#1annetkonings with Copilot wants to merge 2 commits into
annetkonings with Copilot wants to merge 2 commits into
Conversation
Copilot
AI
changed the title
[WIP] Fix failing GitHub Actions job O2 linter
Scope O2 linter push runs to pushed commit range
Aug 3, 2026
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.
The
O2 linterworkflow was failing on push because it linted the full branch divergence frommaster, surfacing unrelated pre-existing violations. This change narrows push-time linting to files introduced by the pushed commit range while keeping PR behavior unchanged.Workflow diff scope
push, file selection now uses${{ github.event.before }}..${{ github.sha }}instead oforigin/${{ env.BRANCH_BASE }}....beforeis all-zero SHA), file selection falls back to files in${{ github.sha }}.Event-specific behavior preserved
pull_request_targetpath is unchanged and still diffs against the base branch via merge-base semantics.Updated run logic (excerpt)