Code-driven issue management, powered by GitHub activity.
GitHub Integration connects GitHub with DevRev so that issues, statuses, and code changes stay in sync in real-time, driven entirely by your team's GitHub activity.
GitHub Integration for DevRev Connect GitHub with DevRev and keep your engineering work in sync across both systems. Issues transition stages automatically based on code activity, and every pull request is tracked as a code change object — giving your team full visibility without manual updates. Overview Link your GitHub activity to DevRev issues by mentioning issue IDs (e.g., ISS-34) in branch names, commit messages, or PR titles. The snap-in routes relevant GitHub events to the corresponding DevRev issue and transitions its stage automatically — from In Development, to In Review, to Closed. If your team follows a branch-to-issue workflow, this snap-in honors that convention and drives issue state from GitHub. Every pull request also generates a code change object that captures the full PR lifecycle: status, author, reviewers, approvals, commit history, timestamps, lines changed, and files modified. Code change objects link directly to the DevRev issues they address, providing a unified view of engineering activity across repositories. Features- Automatic issue status updates: Mention DevRev issues in branch names, commit messages, PR titles, or PR bodies (via /towards and /close commands), and the snap-in transitions issue stages based on GitHub activity.
- Code change tracking: Every pull request generates a code change object that tracks status, reviewers, timestamps, lines changed, and links to related DevRev issues — providing engineering visibility at a glance.
- PR review tasks and inactivity reminders: Review tasks are created for requested reviewers and closed on submission. Inactive PRs trigger reminders on linked DevRev issues after a configurable number of days.
- GitHub slash commands: Use /towards in a PR body to link activity to issues, or /close to auto-close specific issues (or all linked issues with /close #work) when the PR merges.
- Cross-repository engineering insights: Code change objects enable saved views, filters, and natural-language queries across all repositories — surface review bottlenecks, cycle times, and work-in-progress without manual reporting.
More Snap-ins
Build · Import
Jira
Import, migrate, and sync Jira projects with DevRev using flexible one-way or bi-directional sync. Preserve critical fields with recipe mapping and keep both systems up to date.
Grow · Support · Integration
Goodmeetings
Streamline your customers meetings, create summary and action items with Goodmeetings and DevRev
Integration · Automation · Build
PagerDuty Incident Action
Bring in Incidents from PagerDuty into DevRev.
Cloud · Build · Automation
PaaS dim_ticket
PaaS dim_ticket snap-in allows to execute serengeti job periodically to populate data in oasis dataset from datawarehouse.
Computer+ Apps
Our Customers
Initiatives
