Review Taiga's pull requests

On a pull request Taiga opened, any feedback you leave starts a pass. You do not need a Taiga account, and you do not need to mention @taiga. Mentioning it still works.

This page is for the people who review those pull requests. It describes GitHub pull requests; On GitLab covers merge requests.

Where your feedback can go

Each of these starts a pass:

• A comment on the Conversation tab.
• A single comment on a line.
• A review, with or without a summary, submitted as Comment or Request changes. A Comment review with no summary counts when it carries at least one comment on a line.
• Request changes in Taiga itself, described in Request changes.

Every Conversation comment starts a pass, and Taiga then reads it to find what is asked. A comment that asks nothing, such as “LGTM, nice work”, changes nothing and only gets a rocket reaction.

What starts nothing

An approval starts nothing.

Comments from bots start nothing either. Reviews from review bots, such as Copilot, are answered, but only for a limited number of rounds in a row. After that, Taiga hands the pull request back to a person. Feedback from a person resets the count.

See that Taiga has your feedback

Taiga adds an eyes reaction to show it has your feedback. It goes on a Conversation comment, on a review that has a summary, or on the first line comment of a review without one.

Leave several comments at once

The wait starts with the first comment or review that starts a pass, and it does not restart. Comments left within about a minute of the first one are read together in one pass. A comment left later starts the next pass. You can leave several comments before Taiga starts.

What the reply looks like

Taiga answers each request, and each answer says what Taiga did and in which commit, or why it did not. Only a comment on a line is answered in that line’s own thread. A review summary or a Conversation comment is answered in a new comment on the pull request’s Conversation tab, ask by ask.

When Taiga has handled a Conversation comment, it adds a rocket reaction to it.

For what happens to the pull request after a pass, see Runs.

Who can trigger Taiga

On a private repository, anyone who can comment can start a pass, with no Taiga account.

On a public repository, only people with write access or higher (write, maintain, or admin) can. Taiga ignores feedback from anyone else.

Write requests as visible text

Taiga removes hidden content such as HTML comments, invisible characters, image alt text, and hidden elements before it reads a comment. The removal is best effort, not a guarantee. The same markup is also removed from code samples in a comment. Write requests as visible text, and put anything Taiga must act on outside code samples.

On GitLab

On a merge request Taiga opened, a thread starts a pass: a comment on a line, or a comment on the merge request posted with Start thread rather than Comment. A request for changes starts one too. A plain comment on the merge request starts nothing on GitLab yet, so ask in a thread. An approval starts nothing, and neither do the comments of the bot Taiga works as.

Taiga answers each request, and shows it has your feedback with GitLab’s emoji reactions in place of GitHub’s.

If your organization created its own GitHub App

If Conversation comments are slow to start a pass, check how the App is set up. See Integrations and environments for the GitHub App.