01Create the project
On /projects, click "New project", give it a name, and click "Create". The
dialog tells you up front that sources are attached afterwards, so the extra step is not
a surprise. You land back on /projects, where the new project's card shows
"0 sources" and a button to attach one.
02Attach a repository
Open the project, go to its "Sources" tab, and click "Attach a source". Choose the
provider (GitHub is the only one today) and type the repository as
owner/name.
If you have already connected GitHub to your organisation (see connecting GitHub) and the repository is one the installation can see, the attach succeeds immediately, and the "Capabilities" panel beside it starts naming which repository answers for what: reading issues, opening pull requests, and the rest of what a source can be asked to do.
If the repository exists but your GitHub connection cannot see it, the attach is refused
with a message naming the repository and pointing you at
/settings/providers to connect it, or at installing the App on that
repository directly.
You can also attach a repository before connecting GitHub at all, and that succeeds too, deliberately, so creating a project never blocks on which order you did things in. No capability is bound yet, and the project's issues will not list until GitHub is connected: the Specs page says plainly that nothing serves that repository yet, rather than failing silently.
03If the repository has never used Crewbit
A repository missing the three baseline rule files gets them the first time you plan anything on it: Crewbit opens an issue of its own, titled "Add the baseline rules," and plans it before the one you asked for. You review that plan and that pull request the same way you review any other; see the baseline rules guide for what the three files check.
04Remove one, if you need to
Each project's card carries a trash icon. Click it and Crewbit asks you to confirm by naming what goes with it: every Spec under the project, and their Runs and full history, including a Run whose pull request already merged. There is no undo.
A Run still in progress refuses the removal instead of deleting around it: a runner may still be holding its Job. Let the run finish, or cancel it, then remove the project.