GitHub Issues
Automatically create and track GitHub Issues for every CI test failure.
Overview
FixSense can automatically create a GitHub Issue for every failing test it detects. This gives your team a trackable artifact for recurring failures — directly in your repo's issue tracker.
How It Works
- Test fails in CI — FixSense analyzes the failure as usual
- Issue created — A new GitHub Issue is opened with the failure details, root cause, and suggested fix
- Recurring failures — If the same test fails again, FixSense adds a comment to the existing issue instead of creating a duplicate
- Auto-closed on fix — When the test passes again (e.g., after an auto-fix is merged and verified), FixSense automatically closes the issue
What's Included in Each Issue
- Test name and error message
- AI-generated root cause analysis
- Flakiness score
- Suggested fix
- Related code changes
- Link to the CI run and PR
- Auto-fix agent result (if applicable)
Labels
FixSense automatically creates and manages these labels in your repository:
| Label | Meaning |
|---|---|
failsense | All FixSense-tracked issues |
failsense:flaky | Test has a high flakiness score (70+) |
failsense:fixed | Auto-fix agent successfully created a fix |
Enable / Disable
GitHub Issues tracking is enabled by default for all plans.
To toggle it:
- Open your FixSense Dashboard
- Find the GitHub Issues toggle in the usage section
- Click ON or OFF
When disabled, FixSense still analyzes failures and posts PR comments — it just skips issue creation.
Deduplication
FixSense searches for an existing open issue with the same test name before creating a new one. If found, it adds a comment with the new occurrence details. This prevents issue spam for flaky or repeatedly failing tests.
FAQ
Will this create too many issues? No. FixSense deduplicates by test name — recurring failures update the existing issue instead of creating new ones. Flaky tests are labeled so you can filter them.
Can I use this with my existing issue workflow? Yes. FixSense issues are regular GitHub Issues. You can add them to projects, assign them to team members, or reference them in PRs like any other issue.
What happens when I disable and re-enable? Disabling stops new issue creation. Existing issues remain open. Re-enabling resumes issue creation for new failures.