Code review

Open Repositories in your project and click GitHub, GitLab or Bitbucket. Authorize access on the host and choose the repositories. On GitHub this installs the TimetoTest GitHub App. The repository then shows with its default branch.

• GitHub
• GitLab
• Bitbucket

Automatic reviews of new pull requests need the Pro plan or higher.

We review a pull request when it is opened, and again when new commits are pushed. On GitHub, drafts wait until they are marked ready for review.

To review a branch yourself, choose Code task in the message box. Pick the repository and branch under the box and describe what to check.

We build the app from the repository with Railpack, your Dockerfile or your Docker Compose file, and start it in an isolated sandbox. The agent can start PostgreSQL, MySQL or MongoDB next to it.

To set environment variables, the application port and the build method, click the key icon (Edit environment) on the connected repository. With Dockerfile or Docker Compose, also enter the build file. Then click Save configuration.

Each finding appears on the pull request with its location, severity, the evidence from the sandbox and a suggested fix.

On GitHub, mention the TimetoTest app in a pull request comment to ask a follow-up question. It replies in the thread.

These are under Privacy & security on the Repositories page.

• Automatic fixes lets the agent open a pull request that fixes what it found.
• Data retention policy deletes the review conversation when the review finishes. Comments already posted on the pull request stay.
• Strict mode also reviews engineering practice, such as duplication and maintainability. When it is on, you can add Custom code-practice guidance of up to 1,000 characters.

Ask for a fix in a Code task. The agent works on a new branch in the sandbox and opens a pull request on GitHub.

With plan mode on, it writes a plan and waits for your approval before it edits files.