@thegpvc/gp-foundry 0.2.8 → 0.2.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/AGENTS.md +4 -0
- package/README.md +6 -0
- package/actions/config-loader/dist/index.cjs +36 -36
- package/actions/merge-gate/dist/index.cjs +26 -26
- package/actions/run-agent/README.md +56 -10
- package/actions/run-agent/action.yml +141 -18
- package/dist/cli/index.cjs +116 -112
- package/package.json +2 -2
- package/schema/config.schema.json +4 -0
- package/skill/SKILL.md +4 -3
- package/skill/reference/node-types.md +7 -2
- package/skill/templates/foundry.config.yaml +1 -0
package/AGENTS.md
CHANGED
|
@@ -65,6 +65,10 @@ gh secret set CLAUDE_CODE_OAUTH_TOKEN # the coding agent's auth token
|
|
|
65
65
|
gh secret set AGENT_PAT # fine-grained PAT: Contents + Pull requests + Issues + Actions, RW, this repo
|
|
66
66
|
```
|
|
67
67
|
|
|
68
|
+
(Not tied to one person's seat? Set `agent.api_key_secret: ANTHROPIC_API_KEY` in
|
|
69
|
+
`.github/agents/foundry.config.yaml` and have them set that secret instead of
|
|
70
|
+
`CLAUDE_CODE_OAUTH_TOKEN` — an Anthropic API key, usage-billed.)
|
|
71
|
+
|
|
68
72
|
(`AGENT_PAT` exists because the built-in `GITHUB_TOKEN` cannot trigger downstream
|
|
69
73
|
workflows — the pipeline would silently stall between stages.)
|
|
70
74
|
|
package/README.md
CHANGED
|
@@ -68,6 +68,12 @@ repo checks) cleanly when there's no GitHub remote yet, and builds the workflows
|
|
|
68
68
|
| `CLAUDE_CODE_OAUTH_TOKEN` | The coding agent's auth token — how each agent job authenticates to Claude Code. | n/a (agent credential) |
|
|
69
69
|
| `AGENT_PAT` | A fine-grained Personal Access Token used for the agents' git writes, PRs, and comments. Needed because pushes made with the built-in `GITHUB_TOKEN` do **not** trigger downstream workflows, so the pipeline couldn't cascade stage to stage. | Contents · Pull requests · Issues · Actions — **read/write**, scoped to this repo |
|
|
70
70
|
|
|
71
|
+
Prefer an **Anthropic API key** to the OAuth token? The token authenticates as one
|
|
72
|
+
person's subscription seat; a key is usage-billed and belongs to nobody. Set
|
|
73
|
+
`agent.api_key_secret: ANTHROPIC_API_KEY` in `foundry.config.yaml`, run
|
|
74
|
+
`gh secret set ANTHROPIC_API_KEY`, and rebuild — agents then use the key *instead*
|
|
75
|
+
(run-agent takes exactly one credential and refuses both).
|
|
76
|
+
|
|
71
77
|
(`AGENT_PAT` is the default `auth.mode: pat`. You can instead run under a GitHub App
|
|
72
78
|
(`mode: app`, set `app_id_secret`/`app_key_secret`) or the built-in token (`mode:
|
|
73
79
|
github-token`, zero setup but no cascading) — see `foundry.config.yaml`.)
|