Skip to main content

What is Gryndel?

Gryndel reviews your team's merge requests (GitLab) and pull requests (GitHub). When someone opens or updates a merge or pull request, Gryndel reads the change, asks an AI model to look for problems, checks what the model found, and posts the real problems back as comments. On GitLab they come from a user called Gryndel; on GitHub, from your organisation's Gryndel App (shown as <name>[bot]). It works like a colleague who reviews every change within minutes.

Gryndel runs as a hosted service, so there is nothing to install. You open it in your browser at https://app.gryndel.com/ and sign in with your GitLab or GitHub account.

How it works​

  1. Someone opens or updates a merge or pull request.
  2. GitLab or GitHub tells Gryndel through a webhook, an automatic message it sends when something happens.
  3. Gryndel fetches the changed code and sends it to an AI model with instructions and your team's rules.
  4. In most review modes, a second pass checks each suspected problem before it is posted.
  5. Gryndel posts a summary and one comment per finding on the merge or pull request, and can set a pass/fail commit status.
  6. You reply, resolve or dismiss the findings in GitLab or GitHub, as you would with a human reviewer.

Who does what​

WhoWhat they doWhere to start
EveryoneRead Gryndel's reviews in GitLab or GitHub, reply, use @gryndel commands, browse history in the web appSign in
Workspace admins (Owners and Maintainers of a GitLab group, or owners of a GitHub account)Connect their group or account, turn on repositories, choose models, write rulesSet up your team (on GitHub)
Your Gryndel operatorRuns the Gryndel server itself, and sets up its GitLab and GitHub connections. You don't need this guide for that.Ask your IT or platform team

Where to go next​