Forgejo / Gitea setup
Connect one repository.
About two minutes. Ahem installs a signed pull-request webhook and posts advisory reviews without changing your merge rules.
Verify your instance
Create a dedicated scoped token for Ahem. Ahem does not store it until you confirm a repository.
Token permissions
read:user, write:repository, and write:issue. Your account must be a repository admin. On Forgejo, choose “All” repository access: specific-repository tokens cannot call user discovery or repository-admin APIs. Token help ↗For security, hosted Ahem connects only to public HTTPS instance addresses. Repository source is sent through zero-data-retention model routes for review. Data handling
Choose the repository
✓
Ahem is listening.
What happens nextOpen or update a pull request. Ahem will mark the commit as pending, review the bounded Git diff, post one evidence-backed comment, then leave an advisory status.
Your existing branch protections are unchanged. You can remove Ahem at any time by deleting its webhook and revoking its token in Forgejo/Gitea.
Open repository →