Connecting GitHub and GitLab

Loomstack’s Git integrations connect your development workflow directly to your project board. Commits, branches, and pull requests reference tasks automatically, and task statuses update as code moves through review and merge — so no one has to update the board by hand after shipping code.

Connecting Your GitHub Account

1. Go to Settings > Integrations
2. Click Find Integrations and search for “GitHub”
3. Click Connect — you’ll be redirected to GitHub
4. Authorize the Loomstack app and choose whether to grant access to All repositories or Only select repositories
5. Back in Loomstack, map each repository to one or more projects
6. Click Save Mapping

For GitLab, the flow is identical, but you can also connect a self-hosted GitLab instance by clicking Use self-managed GitLab and entering your instance URL plus a personal access token with api scope.

Linking Commits and Branches to Tasks

Every Loomstack task has a short ID (for example, LOOM-482) shown next to its title. Reference it anywhere in your Git workflow:

In commit messages:

git commit -m "LOOM-482 Fix pagination on the reports page"

In branch names:

git checkout -b loom-482-fix-pagination

When Loomstack detects the ID, it attaches the commit or branch to the task’s Development tab, including the author, timestamp, and a link back to the repository.

Automating Task Status with PR Events

You can move tasks automatically as pull requests progress:

1. Go to Settings > Integrations > GitHub (or GitLab)
2. Click Workflow Automations
3. Configure the three default triggers:
   • PR opened → move task to In Review
   • PR merged → move task to Done
   • PR closed without merge → move task back to In Progress
4. Optionally add keywords: including Closes LOOM-482 in a PR description marks the task complete on merge
5. Click Save

Automations respect your project’s workflow — if a project doesn’t have an In Review state, that trigger is skipped.

Viewing Development Activity on a Task

Open any task and click the Development tab to see:

• Linked branches with their latest commit
• Open and merged pull requests, including review status
• Deployment status, if your CI posts deployment events to GitHub/GitLab

Team members without repository access see the activity summary but not code diffs.

Troubleshooting Missing Links

• Confirm the task ID is spelled exactly, including the hyphen (LOOM-482, not LOOM 482)
• Check that the repository is mapped to the correct project under Settings > Integrations
• Commits pushed before the integration was connected are not backfilled — re-push or link them manually from the task’s Development tab with Link commit

Summary

Connect GitHub or GitLab from the Integrations settings, map repositories to projects, and reference task IDs in commits, branches, and PRs. With workflow automations enabled, your board stays accurate without anyone touching it — code review and merge events do the updating for you.