CodeLynq and GitHub

CodeLynq clones your repository, makes the change on a branch of its own and opens a pull request. It never pushes to a protected branch, so nothing reaches main without your review.

Where you enable it, GitHub Actions results and reviewer comments flow back: failing checks and requested changes are picked up and fixed on the same branch, updating the existing pull request rather than opening another one. A merge can trigger your deploy workflow and record the release.

1. Create an access token in GitHub with permission to read the repository and open pull requests.
2. Add the repository in CodeLynq through the guided wizard and paste the token.
3. Let CodeLynq read the repository to propose your stack, conventions and test strategy, then correct what it got wrong.
4. Approve a task and the first pull request appears in your normal review queue.

Actions feedback needs a webhook secret per repository, which you set in the repository settings. Without it CodeLynq still opens pull requests; it just will not iterate on failing checks by itself.

CodeLynq also works with coding agents, GitLab, Bitbucket, GitHub Actions, Fireflies, Plaud, Slack, MCP and webhooks.

• Help: setting up integrations →
• Spec-driven development →
• How it works →
• Pricing →