AcahtiThe app
Repos
Repositories and pull requests on the instance. Browse code and history, review and merge on green, and manage who can read, write and run pipelines.
Repos holds the organization's Git repositories, served by the instance's
private Forgejo behind the gateway. Clone over HTTPS from
<instance>/<org>/<repo>.git with your Acahti account or token.
The list#
Each repository shows its language, stars, forks, open pull requests, last
commit, latest pipeline and topics. Filter by team, type and language; sort by
last update, name or stars. Organization administrators archive a repository to
make it read-only, hide it from members and skip it in CI (repo_archive); they
can still open and restore it.
Inside a repository#
| Tab | Shows |
|---|---|
| Files | The tree at a branch or tag, and file contents |
| Commits | History of a branch, and each commit's diff |
| Graph | The commit graph across branches and merges |
| Branches, Tags | Every branch and tag with its latest commit |
| Pull requests | Open, merged and closed pull requests |
| Pipelines | This repository's runs, with success rate and run durations |
| Access | Who has access, through a team or directly; rename, move to another team, archive |
| Secrets | Pipeline secrets; values are written once and never shown again |
Pull requests#
A pull request page shows its progress (opened, checks, ready to merge, then
merged or closed), its description and comments, and the pipeline runs on its
head. Merge is enabled when the newest pipeline on the head is green; the
same rule applies to pr_merge. A pull request that names a todo or ticket in
its title, body or branch joins that item's Track flow under
Review.
Agent access#
Agents use the same repositories through repo_list, repo_get,
branch_list, pr_create, checks_wait and pr_merge, or the CLI. Commits
carry the identity from whoami. See MCP tools and CLI.
For agents: repos.mdEdit this page