Dogfood docmend on its own repo - #14
Merged
Merged
Conversation
Adds .github/workflows/docmend.yml, triggering on pull_request for changes under packages/*/src/** or any *.md file. References the action locally (uses: ./) rather than a published owner/repo@ref, since it's the same repo and there's no published v1 tag yet - this also means every PR always tests against the action's current code on that branch, not a potentially-stale published version. Restricted the trigger to source/doc-touching paths rather than every PR, given how real the free-tier rate-limit and quota costs turned out to be during the Phase 5 real-repo testing (TESTING.md) - no reason to burn embedding calls re-indexing on a PR that only touches, say, CI config. Requires a GEMINI_API_KEY repository secret to actually run, which isn't something to set up from here - left to be added via the GitHub web UI (Settings > Secrets and variables > Actions) rather than any CLI mechanism, given the earlier incident this session where a key typed via a shell command ended up in the visible conversation transcript. Validated the workflow file is syntactically valid YAML. The actual trigger path can't be exercised by this PR itself, since it only touches .github/workflows/ (matching neither path filter) - real end-to-end verification happens naturally on the next PR that touches source or docs after this merges.
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
1 participant
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
Adds
.github/workflows/docmend.ymlso the repo runs its own tool on its own PRs. Triggers onpull_requestfor changes underpackages/*/src/**or any*.mdfile — restricted rather than every PR, given the real free-tier rate-limit/quota costs measured inTESTING.md's Phase 5 testing (no reason to re-index on a PR that only touches, say, this workflow file itself).References the action locally (
uses: ./) rather thanowner/repo@v1, since there's no published tag yet and this always tests the current branch's code, not a possibly-stale published version.Requires (not part of this PR)
A
GEMINI_API_KEYrepository secret, added via the GitHub web UI (Settings -> Secrets and variables -> Actions) - deliberately not something to set up via any CLI mechanism in this session, given the earlier incident where a key typed through a shell command ended up in the visible conversation transcript.Test plan
npm run lint/typecheck/build(existingci.yml) all pass.github/workflows/, matching neither path filter) - real verification happens on the next PR that touches source or docs after this merges