⛶ Open the code (full-screen explorer)
This page is generated from docs/guide.en.md · Edit this page on GitLab
Project tree plus the file shown in full with the diff in place, syntax highlighting, a mini-map of the changes, navigation between modifications, collapsible panels: three buttons at the top — Report, Tree, Code — each hide their panel. Hiding the code gives the report the full width, to read it comfortably; one panel always stays, the last one refuses to go. Inline comments per line and replies to threads, synchronised with the forge — and editable as long as they are yours.
The tree says what each file carries: the number of unresolved findings (in red when one of them blocks), of discussion threads, of remarks in draft, and of changed lines. On a forty-file merge request, knowing which ones to open meant opening them one by one. The badges stay silent when there is nothing — a tree studded with zeros would be harder to read than the bare tree it replaces.
The whole screen speaks of the REVIEWED version, not of the branch head: tree, file content and line numbers all come from the commit the report describes. That is what makes a “src/foo.js line 137” read in the report land on the right line on the right-hand side, even if the branch has moved since (in which case the merge request is flagged stale anyway). If that commit has disappeared from the repository — a force-push — the screen falls back to the branch head. On the report side, the AI receives the diff already numbered: every line carries its real number in the final version of the file, instead of being left to recount from the @@ headers.
Two ways to comment, your choice. Comment on GitLab publishes right away, as before. Save keeps the remark pending, locally: you review a merge request file by file, and sending them one at a time showers the author with notifications while freezing remarks you would have dropped three files later. A pending comment can be edited and deleted as long as it has not gone out; it shows under its line with an amber border and the words "Waiting to be sent" — rendering it like a published comment would make the work look done. The Send the comments (n) button in the header publishes them all at once; it is also what reminds you that work is waiting, without which you close the merge request leaving your remarks behind.
⚠ Sending asks first and says how many are going out — publishing notifies the author — and whatever fails stays pending, with its reason: a network error on the third comment must not take the first two, nor the half hour of review, with it. The position (file, line, SHAs) is resolved at send time, exactly as for a direct comment: a merge request that moved meanwhile does not receive remarks pinned to a state of the code that no longer exists.
Delete all, next to it, empties the batch in one go. It is the emergency exit: a remark you no longer want — or one the forge refuses because its position is not in the diff — blocks the group send, and used to be removed one by one by reopening each file. The confirmation says how many and which ones: ten remarks written yesterday are not wiped on an anonymous “are you sure?”. Nothing is sent anywhere — these remarks only exist here — and nothing is recoverable afterwards.
In the tree, folders carrying a change are expanded by default and the others are collapsed — but whatever you open or close by hand is remembered for the visit: clicking a file no longer collapses the folder it sits in. The tree starts from the default rule again on the next diff.