Repository navigation
ci: skip Python checks for docs-only changes - #856
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.
Why
Only changes entirely under
website/skipped the Python checks. A README edit, a demo GIF or a regenerated skill docs page still ran the static checks and the unit and integration suites, where unrelated flaky tests could block a docs change.Changes
Treat these as docs-only in
verify.yml, alongsidewebsite/:README.md,CHANGELOG.md,CONTRIBUTING.md,AGENTS.md);.github/demos/(README GIFs);src/sqlbuild/.agents/skills/sqlbuild/references/docs/*.md(skill pages generated from the website docs).Markdown elsewhere, including the hand-written skill files, still counts as code.
Verification
SKILL.md, Python files,pyproject.toml, Markdown undertests/andverify.ymlare not.actionlintreports only the two existingif: falsewarnings.