Guides
How to do the thing, one delivery at a time.
Installing the runner
One command puts the runner on your PATH. The whole path, plus what to do by hand and the one warning macOS shows you if you choose that instead.
Signing in, and what your organisation sees
One way in (your GitHub account), and what belongs to your organisation once you're through.
Creating a project and attaching a repository
A project is where you configure what Crewbit works on. Creating one and pointing it at a repository are two separate steps, on purpose.
Connecting GitHub to your organisation
Separate from signing in: an installation of Crewbit's GitHub App, scoped to the repositories you choose.
Connecting Jira to your organisation
A credential your organisation holds, not a person: a base URL, an email and an API token, so a project can read a Jira source's issues.
Watching a run, and the plan you approve
An issue becomes a run when you say so. It stops once for you to approve the plan, then goes from code to a reviewed pull request on its own.
The baseline rules Crewbit checks for
Three files a repository needs before a run will touch it, read straight from what this build ships, and what happens the first time a repository has none of them.