Code a project and open a pull request
Ask for code in plain words; the agent writes it, opens the pull request, watches CI and fixes failures.
NoBreiniers codes with you. Describe what you want; the agent writes the code, tests it and, if you ask, opens a pull request (PR) and watches its CI until it is green.
Before you start
- The project's folder added under «Projects». See Chats and projects.
- The «For coding» group ready in Settings › Installation.
- For pull requests: access to the repository on GitHub or GitLab. For Bitbucket, Azure DevOps or Gitea, see «Other git hosts» below.
Steps
- Open «New chat in …» from your project.
- For big changes, start in «Plan» and approve the plan. See Plan or Build.
- Ask for what you want, for example «add a button to export to PDF and open a PR».
- The agent works. Watch the changes in the «Changes» panel.
- Before pushing or opening the PR, it asks for approval: «Push … and open a pull request … into …».
- You see «PR #… opened (… → …): … I am watching its CI.» and the «Pull request and CI» bar.
- If CI fails, the agent fixes it by itself: «Fixing the CI of PR #… (attempt … of …)».
- At the end you see «✓ CI is green on PR #…». Say «merge it» if you want it merged; that asks for approval too.
Other things it can do
- Bring a repository, or a PR's code, to a local folder to work on it.
- Reply to review comments and resolve threads.
- Review changes without touching anything, quick or deep. See Code review.
- Follow your project's rules. See Project rules.
PR on autopilot
- In the message box type
/pr autoand send. You may add the title:/pr auto Export to PDF. - The agent opens the pull request, fixes its failed checks and merges it when it passes. You see «PR on autopilot: I fix its failed checks and merge it when it passes.»
Only your command turns it on: the agent cannot put itself on autopilot.
Merge queue
If the target branch uses a merge queue on GitHub, a merge puts the PR in the queue instead of merging it directly, and the agent keeps following it:
| Message | What happens |
|---|---|
| «PR #… is in the merge queue, position …; I keep watching it.» | It waits its turn. The bar says «In the merge queue». |
| «PR #… was taken out of the merge queue.» | The queue let it go. On autopilot, the agent brings the base branch in, fixes it and puts it back in the queue when it passes. |
Other git hosts
Besides GitHub and GitLab, the agent works with pull requests on Bitbucket (Cloud and Data Center), Azure DevOps and Gitea or Forgejo: it opens them, reads their changes and comments, replies, reviews them and merges them.
- Ask for the work as always. The first time, the agent asks you for that host's key.
- Create an access token on the host, with read and write permission on the repository and its pull requests, and paste it when the app asks.
- It is kept encrypted under «Site keys», for that site only. See Site keys.
The key travels only to that host, over a secure connection, and never on a command line. Pushing code still uses your own git.
If something goes wrong
| Message | What it means |
|---|---|
| «PR #… is still red after … automatic fixes: you decide…» | Press «Fix» or tell it in the chat what to do. |
| «I stopped watching PR #…: its checks are still running after 3 hours.» | Check the CI on GitHub. |
| «PR #… has no CI checks: there is nothing to wait for.» | Normal if your repository uses no CI. |
