Branches, commits and PRs now link automatically to Decuga tasks. Here is how the integration works, why it matters, and how to set it up in five minutes.
Every sprint has the same invisible problem: tasks stay on the board long after a developer has started working on them. The engineer pushed a branch on day one, but the task still says To Do because nobody clicked the button. PMs chase status in Slack. Stand-ups cover ground already visible in GitHub. Everyone agrees the sprint board should reflect reality — and nobody has time to keep it in sync.
Connect your GitHub (or GitLab) repository to a Decuga project and the board updates itself. Push a branch named feature/PROJ-42-add-login and the task moves to In Progress automatically. Open a PR referencing the same code and a "Review PR" sub-task is created under the parent task, assigned to the first requested reviewer. Merge the PR and the link card shows "merged." No manual clicks.
Decuga scans branch names, commit message subjects, and PR titles for codes matching the pattern [A-Z]+-\d+ — the same format your task prefix generates (e.g. PROJ-42, API-7, FEAT-100). You do not need any special Git hook or commit convention. If the code appears anywhere in the text, the link is created.
| Where | Example | Result |
|---|---|---|
| Branch name | feature/PROJ-42-login | ✅ Task PROJ-42 linked |
| Commit message | Fix null check — resolves PROJ-42 | ✅ Task PROJ-42 linked |
| PR title | Add OAuth2 [PROJ-42] | ✅ Task PROJ-42 linked |
| Branch name | feature/add-login | ❌ No code found |
Code review is the most commonly skipped step in a sprint. It rarely has a task, so it rarely has an owner, a deadline, or visibility. The integration fixes this: every PR open event creates a sub-task titled "Review PR: <title>" under the parent task, in In Review status, assigned to the first requested reviewer. It shows up on the board, it can be commented on, and it closes when the review is done.
No API credentials required — all event data arrives in the webhook payload itself. The only thing you need to provide is a webhook secret you choose. Decuga gives you a webhook URL. You paste that URL and secret into GitHub → Settings → Webhooks, select Push and Pull request events, and you are done. GitLab works identically.
Install in Decuga
Project Settings → Integrations → Connect GitHub. Enter a webhook secret (any random string).
Add webhook on GitHub
Repo → Settings → Webhooks. Paste the Decuga URL and the same secret. Enable Push + Pull request events.
Push a test branch
Include a task code in the branch name and watch the task move to In Progress within seconds.
This is the first version of the VCS integration. On the roadmap: auto-close tasks when a PR is merged (optional, per-project setting), a project-level dev activity view showing all recent branches and PRs, and support for Bitbucket. If you have a use case we have not covered, the integration architecture is built to be extended — adding a new provider requires implementing a single interface.
Try it today
GitHub and GitLab integrations are available on all plans. Go to Project Settings → Integrations to connect your first repository.
Ready to try Decuga?
Start free — no account or credit card required. One month free trial of the Starter plan.
Start free trial