ci: make required Frontend check report on every PR - #199
Merged
Conversation
mergemaven11
force-pushed
the
fix/frontend-required-check-all-prs
branch
from
August 27, 2026 02:20
e7731b4 to
3445a29
Compare
This was referenced Aug 27, 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.
Problem
Test, lint and build frontendis now a globally required branch-protection check, but Frontend CI only triggers when frontend files change. Docs-only or backend-only PRs can therefore remain blocked waiting for a required check that never starts.Fix
frontend/**or the Frontend CI workflow itself.pushtomainpath-filtered so unnecessary post-merge frontend work is not added.Why this preserves protection
The globally required job still exists and reports on every PR. Frontend changes still run the full existing validation suite, including the real-Chrome click audit. Non-frontend changes no longer wait indefinitely or spend several minutes running irrelevant browser tests.
Merge gate
Do not merge unless Backend, Frontend, and Security checks are green on this exact head, the branch is current with
main, the PR is mergeable, and there are no unresolved blocker comments/reviews.