Pull requests

Tracemoor reads and works on the pull requests of the repository's remote. You open pull requests, review them, comment, merge, and hand open review comments to the AI. The work happens in the Pull Requests tab in the lower area of the Git view. Open it with Git › View Pull Requests.

Supported providers

The provider follows from the URL of the remote origin. Without origin, the first configured remote is used.

For another host the tab shows "Unsupported not supported yet" and the remote URL. GitLab, GitHub Enterprise and Bitbucket Server are not supported.

Each provider needs a token. It is stored once in the operating system's keychain and applies to every project with that provider. See Set up pull requests.

What the integration covers

Work packages open their pull requests through the same connection, with title and description from the Workflow Policy.

Review threads and "open"

A review thread is a comment with its replies. Inline comments belong to a line of a file, conversation comments to the pull request as a whole. A review summary is the text a reviewer writes with a verdict.

Whether a thread still needs action is decided per provider:

GitHub's resolved flag is not available to Tracemoor. A GitHub thread that nobody answered after your last push therefore counts as handled, even if it is not resolved on GitHub.

Notifications

While a project is open, Tracemoor checks its pull requests every minute and fetches the remote every three minutes. Changes appear under the bell icon in the top bar: a new pull request, approved, changes requested, merged, closed, and merge conflicts. The number on the bell counts unread events. Opening the list marks them as read, Clear empties it. Click an event to open the pull request in the browser.

Only changes after the project was opened are reported. The list is kept per project. Checks only run when a token for the provider is configured.

Differences between the providers