Link GitHub to Acta

An owner or admin opens Workspace settings → GitHub, connects the Acta GitHub app, and links each repository to a board. A repository belongs to one board, and a board can have several. The repository pickers suggest boards with the same name.

Put the task's id in a branch name, a pull request title or a commit message, and it links:

• A branch like act-12-add-csv-export. Each task has a Copy branch name button.
• A pull request title like “ACT-12 Add CSV export”.
• A closing keyword in the pull request's description: “Fixes ACT-12”, “Closes ACT-3, ACT-4” or “Resolves ACT-7”.

• A branch or commit that names a task moves it to in progress.
• An open pull request moves it to review. A draft keeps it in progress.
• A merged pull request that names the task in its branch, title or a closing keyword moves it to done.

Tasks only ever move forward, and each step can be turned off per repository. Acta can also leave one comment on each pull request listing its tasks, kept up to date as the list changes.

For work that didn't name the task, paste the address of a pull request, issue, branch or commit into the task's Development section. Agents can do the same with link_github.

Turn on Sync issues for a repository and its issues come over as tasks, only ones with a chosen label if you set one. After that:

• Title, status and labels stay in step both ways, and the later edit wins.
• Comments made on GitHub come into Acta, and comments made in Acta go to the issue, unless Send comments to issues is off.
• An issue closed as not planned moves its task to canceled.
• Open issue in a task's Development section, or open_github_issue for agents, turns a task into an issue.

Changes from GitHub are marked “via GitHub” and made as the member who linked that GitHub account under Account, or else as whoever connected GitHub.