Closing: the minimum permissions are documented in guides/credentials.md with the evidence per API call (Gitea source: read:repository, repository administrator for push_mirrors; GitHub documentation: Administration: Read and write, Metadata: Read automatic), and are approved by S01 standing in for S05 (ADR-0002, PR #66).
Not done: they have not been tested on this instance with a token that holds only these permissions. The optional check list is in the guide; if it is run, record the result here or in a new issue.
Closing: the minimum permissions are documented in `guides/credentials.md` with the evidence per API call (Gitea source: `read:repository`, repository administrator for `push_mirrors`; GitHub documentation: `Administration: Read and write`, `Metadata: Read` automatic), and are approved by S01 standing in for S05 (ADR-0002, PR #66).
Not done: they have not been tested on this instance with a token that holds only these permissions. The optional check list is in the guide; if it is run, record the result here or in a new issue.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Determine the minimum Gitea token scope and GitHub fine-grained token permission that the sync needs, and document them.
Phase: MIL-002
Closing: the minimum permissions are documented in
guides/credentials.mdwith the evidence per API call (Gitea source:read:repository, repository administrator forpush_mirrors; GitHub documentation:Administration: Read and write,Metadata: Readautomatic), and are approved by S01 standing in for S05 (ADR-0002, PR #66).Not done: they have not been tested on this instance with a token that holds only these permissions. The optional check list is in the guide; if it is run, record the result here or in a new issue.