Would the project be open to a PR adding Forgejo support to tkn pac create repo and tkn pac webhook add?
The CLI webhook setup path currently only supports GitHub, GitLab, and Bitbucket Cloud. The Forgejo docs also say these CLI flows are not supported today.
Proposed scope:
- Add
forgejo to CLI webhook provider selection.
- Use the existing vendored Forgejo SDK to create repository webhooks.
- Configure the Forgejo events PAC already handles:
push, pull_request, and issue_comment.
- Reuse the existing Repository CR / Secret update flow used by other webhook providers.
- Update Forgejo docs for CLI setup.
One token caveat: Forgejo webhook creation requires repository-admin capability. Tokens limited to "Specific repositories" or "Public only" can fail even with write:repository, so the CLI/docs should ask for repository access All plus write:repository and write:issue if using the cli.
Would the project be open to a PR adding Forgejo support to
tkn pac create repoandtkn pac webhook add?The CLI webhook setup path currently only supports GitHub, GitLab, and Bitbucket Cloud. The Forgejo docs also say these CLI flows are not supported today.
Proposed scope:
forgejoto CLI webhook provider selection.push,pull_request, andissue_comment.One token caveat: Forgejo webhook creation requires repository-admin capability. Tokens limited to "Specific repositories" or "Public only" can fail even with
write:repository, so the CLI/docs should ask for repository accessAllpluswrite:repositoryandwrite:issueif using the cli.