For teams that ship code, AspirePro links delivery work to the repositories it lands in. GitHub and self-hosted Gitea are both first-class.
Connecting#
An administrator connects under System → Integrations → Git: add a connection with a token, then choose which repositories AspirePro should watch. Webhooks keep activity flowing in as it happens.
What you get#
- Branches, commits, and pull requests linked to tasks — a task shows the code that implements it, with live status (PR opened, merged, closed).
- Auto-linking from branch names — name a branch after a task token (for example
AP-142-fix-header) and the link happens on its own; no manual attaching. - Notifications — task followers hear when a PR for their task opens, merges, or closes without merging.
- Repo activity — recent branches, commits, and PRs per repository, visible from the integration pages.
Where it's controlled#
Git linkage is opt-in per project or planner — teams that don't ship code never see Git chrome on their boards. Enable it in the project's or planner's settings, pick the repositories that matter, and the task panel grows its Git section. See Git links for the task-side experience.