jschoubben aaf341a2d8 gitea: the token needs read:user, not just write:repository and write:issue ...

Deployed #49 and the watcher immediately broke: GET /user/repos answered 403,
'required=[read:user]' — confirmed live against the running forge (1.27.3).
That route sits under gitea's user scope category despite listing
repositories, not repository as assumed.

Also gives the fake forge real scope enforcement on /user/repos, which is
why the original PR's test suite didn't catch this: it only checked the
token's value was valid, never that it carried the required scope.

2026-09-24 11:43:46 +02:00

..

provisioner

gitea provides the package registry; the builder gets its npm credential

2026-09-16 10:27:26 +02:00

test

gitea: the token needs read:user, not just write:repository and write:issue

2026-09-24 11:43:46 +02:00

tools

The forge mints its own API token with the admin account the vault delivers

2026-09-23 23:48:36 +02:00

client.ts

The forge mints its own API token with the admin account the vault delivers

2026-09-23 23:48:36 +02:00

Dockerfile

The forge mints its own API token with the admin account the vault delivers

2026-09-23 23:48:36 +02:00

index.ts

The forge mints its own API token with the admin account the vault delivers

2026-09-23 23:48:36 +02:00

module.json

The forge mints its own API token with the admin account the vault delivers

2026-09-23 23:48:36 +02:00

package.json

The forge mints its own API token with the admin account the vault delivers

2026-09-23 23:48:36 +02:00

token.ts

gitea: the token needs read:user, not just write:repository and write:issue

2026-09-24 11:43:46 +02:00

tsconfig.json

The forge mints its own API token with the admin account the vault delivers

2026-09-23 23:48:36 +02:00