Software teams live in GitHub, but project context lives in Pulse. The Pulse + GitHub integration closes that gap by linking pull requests, commits, and issues directly to the tasks and milestones they belong to, giving every stakeholder, technical or not, a clear picture of where development work stands at any given moment. Instead of chasing engineers for updates or manually reconciling a task board with a repository, everyone in the organisation can see real development progress reflected automatically in Pulse.
What the Integration Does
Once connected, Pulse listens to activity across your linked GitHub repositories and reflects that activity on the relevant task cards. Pull request status (open, review requested, merged, closed) appears on the associated Pulse task automatically. Commits can be linked by referencing a Pulse task ID in the commit message, creating a traceable thread from a line of code back to the original requirement. Branch names, reviewer assignments, and CI status checks are also surfaced inside Pulse so non-technical team members have full context without needing a GitHub account.
Key Use Cases
- Automatic task progress from PR status: When a pull request linked to a Pulse task moves from open to merged, the task status updates to Done automatically, with no manual ticking required and no risk of Pulse falling out of sync with actual delivery.
- Sprint velocity tracking: Pulse aggregates GitHub merge data across a sprint to calculate how many story points were delivered versus planned, surfacing velocity in the dashboard without any manual data entry from developers or project managers.
- Bug triage workflow: GitHub Issues labelled as bugs can be imported into Pulse as tasks, assigned to team members, and prioritised within a sprint, turning raw issue reports into scheduled, trackable work with full history preserved.
- Release milestone alignment: Map a Pulse milestone to a GitHub release tag. When the tag is created, Pulse automatically closes the milestone and notifies stakeholders, keeping your project timeline honest and eliminating the need for a separate release communication.
How to Set It Up
Go to Settings > Integrations > GitHub in Pulse and click Connect GitHub. Authenticate via GitHub OAuth and select the repositories you want to link. Back in Pulse, open any task and use the GitHub panel on the right sidebar to attach a pull request or issue by URL or search. To link commits, add pulse:#TASK-ID anywhere in your commit message. Repository and task mappings can be updated at any time, and you can connect multiple repositories to a single Pulse project if your codebase spans several repos.
Bridge the gap between code and project delivery. Try Pulse free for 14 days and see your GitHub activity inside your project board from day one.