Repository navigation
chore: drop probe residue so the stack lands workflow changes only - #940
Closed
thekevinbot wants to merge 1 commit into
Closed
thekevinbot wants to merge 1 commit into
thekevinbot wants to merge 1 commit into
Conversation
The stack's docs layer added a trailing blank line to prove the restored docs-ci trigger fired. It served that purpose and is the only non-workflow content the stack would otherwise land on main -- where it is also the only file matching docs-release's push paths, so it would trigger a docs site redeploy for no reason. With this reverted the stack lands workflow changes and nothing else.
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.
Cleanup layer of #834, the new top of the stack. Base is #902.
Reverts the one blank line the docs layer added to
docs/index.md. That line existed to prove the restoreddocs-citrigger fired — it did, repeatedly — and it is the only non-workflow content the stack would otherwise land onmain.It is not inert. It is the only file in the whole stack matching
docs-release.yml's push paths, so leaving it in means the merge triggers a docs site redeploy purely to publish a trailing newline.What the stack lands after this
Verified against
main:docs-ci,internals-checks-ci,internals-distcheck-ci,plugin-dirsql-embedding-cipython-test→dirsql-python-ci,rust-test→dirsql-rust-ci,ts-test→dirsql-typescript-ci,docs→docs-release,release-precheck→release-ci,release-config-check→putitoutthere-config-checkconventions,plugins-test,python-lint,python-typecheck,ts-lint,ts-typecheckchangelog-checkNothing outside
.github/workflows/. No source files, so noruff/biome/cargo fmtexposure on the merge push, and no package globs match, sorelease.ymlpublishes nothing.Out of scope, noted
git ls-treeturns up 19 accumulated e2e attestation receipts across four packages, including one named for a long-gone branch (internals/checks/e2e-attestations/claude-775-probe-abspath.json). These are pre-existing onmain, not introduced by this stack, and pruning them touches whate2e verifywalks for freshness. Left alone deliberately; worth its own issue rather than a drive-by deletion here.Expected checks
docs-ci(build) —docs/**matches, which also re-verifies the docs build against the revert.E2E Verification
N/A - docs whitespace revert, no source change
Generated by Claude Code