DocsIntroduction
Docs/Get started

Introduction

Anvil reviews your pull requests, runs your CI and hosts your code, in one place at itest.wicker.life. It works with repositories on GitHub and repositories hosted on Anvil.

What Anvil does #

What you get
Code review A walkthrough of every pull request, inline findings with severities and suggested fixes, and a fresh look at every push. Ask questions with @anvil and teach it rules that stick.
CI runners runs-on: anvil-4cpu runs a GitHub Actions job on Anvil's machines, with the Actions cache, Docker layers and git on the same disk.
CI insight Run history across repositories, failure explanations on the pull request, flaky jobs and tests, log search, monitors and runner sizing.
Hosting Repositories on Anvil with issues, pull requests, merges and CI, and nothing to install.
Agents An MCP server, so a coding agent can read reviews, fix findings, run workflows and read logs.

Review and CI share what they know: when a job fails on a pull request, Anvil reads the log and the code and tells you why in the pull request.

How access works #

Anvil is invitation only.

  1. Request access and say what you'd use it for.
  2. Open the invite you get by email, and create your account with that address or with GitHub.
  3. Follow the setup checklist on the Overview. It ticks each step off as it happens.

Signing in #

There are no passwords. On the sign-in page you can:

  • get a sign-in link by email (it works once, for 15 minutes);
  • Continue with GitHub, once GitHub is connected to your account;
  • Continue with Gitea, if you used it before.

All of them lead to the same account when the email address matches. Settings → Account shows your address and lets you connect GitHub to an account you started with email.