notify-intent workflow assumes library is in TanStack org

[eluce2]

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-check

Expected behavior

For libraries outside the TanStack org, either:

1. Skip generating notify-intent.yml entirely (the local check-skills.yml already handles staleness detection on release), or
2. Make the target repository configurable (--notify-repo flag or prompt), or
3. 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

[Nick-Lucas]

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

[KyleAMathews]

This was a mistake and should have just referenced the repo it was running in. It's now fixed on main.