Skip to main content

Frequently asked questions

Does Gryndel work with GitLab and GitHub?​

Yes. It reviews merge requests on GitLab (self-managed or GitLab.com) and pull requests on GitHub (github.com or GitHub Enterprise Server), if your operator has connected them. Each workspace is on one of them: a GitLab group or a GitHub account. A sign-in is on one too, so if your teams use both, sign out and sign in with the other to switch. See Sign in.

Where does my code go?​

To the Gryndel server, and from there to the model provider your workspace uses. With a hosted provider, that company receives the code under review, with secrets filtered out as far as Gryndel can. With your own model server, it stays on your network. Your workspace admins choose the provider in Model settings.

Does Gryndel keep a copy of my code?​

Not by default. With Don't keep code, Gryndel fetches the code from GitLab or GitHub for each review and afterwards keeps only each finding's location and title. The full comments stay on the merge or pull request. Admins can choose otherwise per repository on the Data tab in Repositories, unless it's enforced for everyone.

Why do I only see some workspaces?​

You see workspaces for the GitLab groups or GitHub accounts you belong to, on the host you signed in with. Gryndel never shows you a group or account that GitLab or GitHub doesn't let you see.

Why is Gryndel called <name>[bot] on GitHub?​

On GitHub, Gryndel is a GitHub App, and GitHub shows an App's comments under its name with [bot] after it. The name is the one your operator gave the App. On GitLab, Gryndel is a user, usually gryndel.

Why doesn't @gryndel autocomplete on GitHub?​

An App can't be @-mentioned on GitHub, so GitHub doesn't suggest it or send a notification. Gryndel watches new comments for the word itself. Type @gryndel and the command in full. Your operator can choose a different word; your team will know if they did.

Who can use @gryndel commands?​

On GitLab, people with the Developer role or higher in the project. On GitHub, people with write access to the repository. Others get a short reply saying so. On GitHub, comments from bots are never treated as commands. See Talking to Gryndel.

Can Gryndel change my code or settings?​

Gryndel's GitLab user is a Developer of your group. It can comment, resolve its own threads and set commit statuses. If a repository uses Suggest and apply fixes, it also commits its suggested fixes to the source branch.

On both, when an admin uses Learn a repository, Gryndel opens a merge or pull request with its notes from a branch of its own, for your team to review. It never merges, approves or changes repository settings.

Will it block my merge or pull request?​

It sets a commit status, gryndel/review. By default only the most serious findings (P0) make it fail. Your admins can change that. Whether a failed status blocks merging depends on your settings: on GitLab, the project's merge request settings; on GitHub, whether a branch protection rule or ruleset requires the status (see Prepare your GitHub account).

How do I stop it reviewing one merge or pull request?​

Comment @gryndel pause, and @gryndel resume to start again.

Gryndel keeps flagging something that's fine​

Reply @gryndel ignore this in the thread so it isn't raised again on that merge or pull request. Ask an admin to add a rule, or teach one yourself with @gryndel learn: <what to remember>.

What does it cost?​

The Costs page shows what reviews cost in your workspace, by provider and model.