GitHub Issues
Connect DontBreak to GitHub and every test failure becomes an issue in your repository — complete with the failed steps, error messages, screenshots, and a link back to the full report. When the test passes again, the issue is closed automatically. Your bug triage happens in the same repo where your team already ships code, with no copy-pasting.
Connecting GitHub
Go to Automation > Projects in the sidebar, where GitHub Issues sits alongside Trello under Project Management.
Click Connect with GitHub
You're sent to GitHub's authorization page. DontBreak requests the repo scope so it can open issues in your repositories — including private ones. Approve the request and you'll be redirected back to the Projects page, now connected.
Choose a repository
Pick the Repository where issues should be created. The dropdown lists the repos you own or collaborate on.
Pick a Label (optional)
Choose a Label to apply to every issue DontBreak opens — for example bug or qa. Leave it empty to create issues with no label.
Save and test
Click Save Configuration, then Test Connection to confirm DontBreak can reach your GitHub account and the selected repository. You'll see "Connection successful!" if everything is wired up.
What gets created on failure
When a test fails, DontBreak opens an issue in your configured repository:
- Title:
[FAIL] Test name — browser device, so you can see at a glance what broke and where (e.g. which of your browsers and devices). - Body: the test name and URL, browser, device, and run time, followed by each failed step with its error message, screenshots of the failed steps embedded inline, and a View Full Report link to the run in DontBreak.
- Label: if you configured one, it's applied to the issue.
No duplicate issues
DontBreak keeps one open issue per test. If the same test fails again while its issue is still open, the existing issue is kept and updated to point at the latest run instead of cluttering your repo with duplicates.
When the previously failing test passes again, DontBreak automatically closes the open issue (with a completed state reason) — your repo reflects the real state of your tests without anyone triaging by hand.
Testing the connection
Use the Test Connection button on the Projects page any time to confirm DontBreak can still reach GitHub and the selected repository. It's the quickest way to check the integration is healthy — much better to catch a problem now than to discover a real failure never got filed.
Disconnecting
At the bottom of the Projects page, click Disconnect GitHub. This removes the integration and stops issue creation immediately. Existing issues stay in your repository — DontBreak never deletes them. You can reconnect any time from the same page.
Warning
If you revoke DontBreak's access from inside GitHub (rather than disconnecting here), the integration disables itself automatically the next time it can't reach GitHub. Reconnect from the Projects page to re-enable it.
Troubleshooting
- Issues stopped being created. The GitHub token was most likely revoked from your GitHub account settings, which disables the integration automatically. Click Connect with GitHub on the Projects page to reconnect and re-enable it.
- The configured repository was renamed or deleted. Open the Projects page, pick the repository again from the Repository dropdown, and click Save Configuration. Run Test Connection to confirm the new selection works.
Works well with
- Slack — get the instant alert in chat while the GitHub issue tracks the fix.
- Understanding test results — what you'll find behind the issue's report link.
- Scheduling — scheduled runs plus GitHub Issues means overnight failures are already filed in your repo by morning.