CoincideFeature
Commits, pushes and pull requests
When an agent’s work is ready, ship it from the diff panel: one action can create a branch, commit, push and open the pull request, with the message and description written by the thread’s own agent. For GitHub, a pull request workspace sits beside the conversation.
The Git actions button
At the foot of the diff panel a bar shows the branch, how it stands against its upstream, and a Git action button: a primary action for the current state plus a menu with Commit…, Push, Pull and Create Pull Request (Create Merge Request on GitLab). Actions run in sequence, so one click can commit, push and open the request. Pushing to, or opening a request from, the default branch asks first.
Committing
The commit sheet lists the changed files to include and a message field. Leave the message empty and the thread’s agent writes one from the changes you’re committing. Use a Feature Branch creates a branch named after the change and commits there, which is handy when you’re on main.
The agent writes commit messages and pull request descriptions in a separate read-only session: it runs in plan mode and every approval is declined, so it can’t change anything. For a pull request it also gets a summary of the thread that made the change. If no agent is ready or it doesn’t answer in time, Coincide falls back to a plain summary of the changed files or commits.
Pull and merge requests on five hosts
Coincide reads the repository’s remote to tell which host it’s on, then uses that host’s own command-line tool with your existing sign-in. Nothing goes through a Coincide server.
| Host | How the request is opened |
|---|---|
| GitHub (and GitHub Enterprise) | GitHub CLI, gh |
| GitLab | GitLab CLI, glab, as a merge request |
| Azure DevOps | Azure CLI, az, with its azure-devops extension |
| Forgejo and Codeberg | Gitea CLI, tea, which signs in to Forgejo servers |
| Bitbucket | On the web: Coincide opens Bitbucket’s page for creating the pull request |
If an existing request already covers the branch, Coincide finds it instead of opening another. Without the host’s CLI signed in, hosts other than GitHub open their web page for creating the request. Coincide runs these tools so they never prompt and never install or update anything.
The GitHub pull request workspace
View › Show Pull Requests opens a panel beside the conversation, sharing the inspector with the diff, for the thread’s repository on GitHub. It lists Open Pull Requests, My Pull Requests or Review Requested, and for one pull request shows its description, reviews and checks with their status. From there you can:
- Review…: approve, comment or request changes with a message. The review is attached to the exact revision you looked at.
- Merge…: create a merge commit, squash and merge, or rebase and merge, as the repository allows. Coincide merges the revision you reviewed, so commits pushed after you looked aren’t merged by surprise. The branch stays, local and remote.
- Mark Ready for Review for a draft.
- Check Out in New Thread: creates a worktree on the pull request’s branch and opens a thread in it, so an agent can work on the PR without touching your checkout. It uses
gh pr checkout, which also handles branches from forks. - Mention in Message, or type
#in the composer, to link a pull request in what you send.
What you need
- The host’s CLI installed and signed in, for example
gh auth login. The pull request workspace needsghand a repository on GitHub; for other hosts it says the repository is elsewhere. - A remote to push to. Without one, only Commit is available.
- Committing works in any Git repository, including a thread’s worktree.