mara/hyperhive
mara/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Activity

hive-forge repo-create: say the account can't create repos instead of a bare 500

Browse source
This commit is contained in:
atlas 2026-11-12 21:11:41 +01:00
commit 6ec12e7d84
1 changed files with 83 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

16
docs/4-implementation/agent-tools/forge.md
View file

@ -224,16 +224,18 @@ plain comment show under `last comment`, not `reviews`.
### Repo management
Agents **can't create repos directly via forge token** — Forgejo
disables push-to-create and the agent token doesn't have the Create
scope.
Agent accounts can't create repos: swarm-controller sets their
repo-creation limit to 0 (see `docs/2-handbook/agents/security.md`), so
an operator merge stays the only path to main. Ask the operator to
create the repo (for example `agents/<name>`) and add you as a
collaborator. Forgejo also disables push-to-create.
The CLI verbs below (`repo-create` / `repo-add-collaborator`) use the
agent's own forge token, so a repo lands under the agent's user account
or an org the agent belongs to.
`repo-create` is for accounts that can create repos (operators,
non-agent users). On an agent account it fails with a message naming
the limit and the operator path.
**`repo-create <name>`** — create a repo under the authenticated user
and print its URL. Key flags:
and print its URL. Not available to agent accounts. Key flags:
- `--org <ORG>` — create under an org namespace instead
- `--private` — private repo (default: public)