GitHub
Link repositories to projects and pull requests to tasks, get notified when pull requests open or merge, and move tasks to done on merge.
Connect GitHub to link a repository to each project and pull requests to tasks. When a linked pull request opens or merges, the people on the task are notified, and a merged pull request moves its task to done.
What you need first
- A GitHub account with access to your agency's repositories.
- Owner or admin access in OpsDash to connect it.
- GitHub credentials for your OpsDash. If the GitHub card asks you to Configure credentials, create a GitHub OAuth app, add the redirect URI shown on the card, and paste its Client ID and Client Secret.
Connect
- Go to Settings › Integrations and choose Connect on GitHub.
- Approve access in GitHub. OpsDash asks to read your repositories and organisations.
- On Settings › Integrations › GitHub, choose Test connection.
Link a repository to a project
Open the project's Settings › Integrations and, under GitHub Repository, choose from your repositories, or type owner/repo (or paste its github.com address; this works before GitHub is connected). Unlink removes it.
Link a pull request to a task
In the task panel, under Pull request, choose Link PR and paste the pull request's address. Link more than one with Link another PR.
Webhooks: notifications and moving tasks
So OpsDash hears when pull requests open or merge, add a webhook in each repository:
- In GitHub, open the repository's Settings › Webhooks › Add webhook.
- Paste the payload URL shown on OpsDash's GitHub page.
- Set the content type to application/json.
- Set the secret to your OpsDash's GitHub webhook secret (it's set by whoever runs your OpsDash; on opsdash.io, ask support).
- Choose Let me select individual events and tick Pull requests.
Then, for tasks linked to a pull request in that repository:
- the people on the task get a notification when it's opened, closed or merged,
- a merged pull request moves the task to the project's done status.
The Sync log on OpsDash's GitHub page shows recent webhook activity.
Troubleshooting
- The task didn't move on merge: check the pull request is linked on the task, the repository matches the project's, and the webhook shows a successful delivery in GitHub.
- Webhook deliveries fail with 401: the secret doesn't match.
- "GitHub isn't connected" in a project: connect it in Settings › Integrations. If it stopped working, Test connection, and reconnect if GitHub still refuses.
Settings in OpsDash
These open in OpsDash. You’ll be asked to sign in first if you aren’t already.
Related articles
- The task panelCreate tasks, and set their status, people, dates, estimates, phase, sprint, tags, custom fields and recurrence from the task panel.
- ProjectsCreate a project, choose how it's organised, and use its overview, settings, status updates and templates.
- FigmaLink Figma design files to projects and tasks, with thumbnails and an Open in Figma button.