Repository navigation
notify-intent workflow assumes library is in TanStack org #76
Description
Problem
setup-github-actions generates a notify-intent.yml workflow that dispatches a repository_dispatch event to TanStack/intent on every push to main. This requires a fine-grained PAT with contents:write on TanStack/intent, which third-party libraries cannot obtain.
The workflow is hardcoded to notify TanStack/intent:
- name: Dispatch to intent repo
uses: peter-evans/repository-dispatch@v3
with:
token: ${{ secrets.INTENT_NOTIFY_TOKEN }}
repository: TanStack/intent # hardcoded
event-type: skill-checkExpected behavior
For libraries outside the TanStack org, either:
- Skip generating
notify-intent.ymlentirely (the localcheck-skills.ymlalready handles staleness detection on release), or - Make the target repository configurable (
--notify-repoflag or prompt), or - Document that this workflow is TanStack-internal and not needed for third-party libraries
Current workaround
Delete the generated notify-intent.yml. The check-skills.yml workflow covers staleness detection independently.
Environment
@tanstack/intent: 0.0.19- Monorepo: pnpm workspaces
Reacted by Nick Lucas
Metadata
Metadata
Assignees
Labels
No labels
Activity
Nick-Lucas commentedon Mar 15, 2026
Glad I'm not the only one a bit confused by this, would be cool to have a webhook we could call with some kind of key for provenance, but I was baffled because this is both in the docs and in my own codebase now too, but it probably can't work for anybody outside of the Tanstack org
fix: replace hardcoded TanStack/intent with github.repository in noti…
fix: replace hardcoded TanStack/intent with github.repository in noti…
KyleAMathews commentedon Mar 15, 2026
This was a mistake and should have just referenced the repo it was running in. It's now fixed on main.
Add back notify-intent workflow for trigger skill review