For teams on GitHub with Copilot who want a first fix for a bug without writing it by hand.
Your setup
- App code in a GitHub repository.
- A Copilot plan that includes the coding agent. On an organization repository, an owner has turned on the coding agent policy for that repository.
- Certyn found a bug and you agree it is real.
Say this to Certyn
Issue 12 is real. Send it to Copilot for a fix PR against main.
What Certyn does
- If GitHub is not connected for coding yet, opens the GitHub connect form for coding. You authorize GitHub, then pick the repository and base branch. You can also do this on the Coding tasks page.
- Asks before it starts, because the task writes to your repository and uses your Copilot plan.
- Sends the issue to Copilot (
app.codingtask.create): title, report, severity, the environment and build where it was found, and a link back to the issue. - Reports the task status when you ask: what coding tasks are running? Status is Queued, Running, Needs input, Succeeded or Failed.
- After the PR is merged and deployed, you say retest issue 12. Certyn runs the bug again and records the result on the same issue.
What you get
- A pull request from Copilot on its own branch, for your normal review.
- The task and its PR link on the issue and the Coding tasks page.
- A retest result that shows if the fix works.
Limits
- Certyn never merges and never pushes to your base branch. You review and merge the PR.
- Certyn cannot stop a running Copilot task. Stop it on GitHub.
- Without a Copilot plan that has the coding agent, the task fails. Retrying does not help; check the plan and the repository policy.
- Claude Code, Cursor and other MCP clients cannot start a coding task. Use Ask Certyn.
- The feature must be on for your workspace. Then Coding tasks shows in the top navigation.