The Source Code integration puts your GitHub and GitLab work on the task. Linked issues, branches, and pull or merge requests appear in a Source Code section on the task, together with their build and deploy state. Provider events keep the section current, so the whole team can see where work stands, and developers can drive the task forward from the tools they already use.
What you can do
- Connect a GitHub or GitLab repository to a project.
- Link a task to a branch or a pull or merge request, by hand or automatically.
- Unlink issues, branches, and pull or merge requests from a task.
- Complete a task when its pull or merge request merges.
- Run short commands from a commit or a pull request to log time, set an estimate, assign, label, comment, or relate tasks.
- Read the state of the work in the Source Code section and the pipeline graph.
- Scan the Source column in List view to find tasks with failing checks or other code activity.
- Archive a GitHub or GitLab connection and restore it by connecting it again.
- Use an AI agent to suggest branch names, inspect linked work and its history, find project repositories, and link existing work.
- Check what a provider sent in the Webhook Logs.
See Use Source Code with AI agents for the Source tools available through the ActiveCollab MCP server.
Which providers work
- GitHub on github.com, through a GitHub App.
- GitLab on gitlab.com and on a self-managed GitLab server.
GitHub Enterprise Server (self-managed GitHub) is not supported in this version. Self-managed hosting applies to GitLab.
Who it is for
- People who plan, bill, and talk to clients see where a task stands without asking a developer.
- Developers link their work with almost no effort, and act on tasks from commits and pull requests.
- Clients see linked source only where a project turns it on. This setting is off by default.