Run required docs check on every PR - #257
Merged
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
mainWhy
The
main - required checksruleset requires thehtmljob for every pull request. The workflow's pull-request path filter prevented that job from starting when a change did not touch documentation, Python source, project metadata, scripts, orCONTRIBUTING.md. GitHub then left the requiredhtmlcontext in an indefinitely expected state and blocked otherwise valid pull requests.Impact
Every pull request now reports the required
htmlstatus. Scheduled behavior and path-filtered validation after pushes tomainremain unchanged.Validation
actionlint -shellcheck= .github/workflows/docs.ymlyamlfixand generated ownership checkshtmlrequirementactionlintwith ShellCheck enabled still reports the existing SC2129 style warning in the workflow summary step; the same warning is present onorigin/mainand is outside this fix.