Adding a project
Lesson 8 of 10 · 3 min 56 s. Add a project agents can work in safely. Give it the repository's address, set the branch agents deliver into and the checks every change must pass, say who works in it, and have the Repo Wizard get the repository ready for agents.
Before you start
- You have done Scheduled tasks and are signed in to the console.
- The address of the repository the project works in. In the example, TimeSaver (a time-tracking app for small teams) adds Invoicing on its own app repository.
- At least one machine online on Nodes, where the project's tasks will run.
- A group of the people who will work in the project, like the TimeSaver developers group.
Steps
-
Click Directory, in the sidebar. It opens on Projects. Each project is a repository agents work in, with the team's rules for it: where to deliver, what to check, and who may ask for work.
-
Press + (Add project). The New project page opens beside the list. It asks one question at a time, and the step bar at the top shows where you are. Under What are you making?, pick App / Website: the page moves on by itself.

-
Under Is it new or existing?, pick Existing: the repository is already there.
-
On Details, under Connect your repository, give the repository's address under Repo URL. Integration branch is where agents start from and deliver into; here it is
develop. Name the project the way the team will say it: Invoicing. Under the fields, What happens next says that creating the project starts its setup.
-
Press Create project. As an org admin you put the project on the organization's enabled machines, and the new project's Tasks open.
-
The onboarding task is already being worked on, at the top of the list. It finds and writes down what agents need: the instructions they read first, and the commands that start and check the app. It runs Guided, so it asks before key decisions; answer it as you would any other task.
-
While it works, open the project and go to Settings. Under Branches, Read only is off, so agents can deliver their changes to the branch. Under Testing, type the check every change must pass into Quick gate command: it runs while the agent works. Type the full check, run before a change merges, into Full gate command (on a custom pipeline it is the Merge step's gate on Pipeline instead). A change that fails either never reaches the branch. Press Save.
-
Under Settings, pick Access and press Grant access. Under Who, pick the group that works in the project, and leave Role at Project Developer, so they can file the project's tasks and follow them. Press Add. Everyone in the group now has the project in their console, and nobody outside it does.
-
When the onboarding task has finished, open it and go to Details. Under Outcome, the Repo Wizard says what it found and what it set up. If the repository was already ready, no code changes; instead it fills in the project's settings itself, such as the commands that start and stop the app and the gate commands, after running each one to check it works.
What you learned
- Projects live under Directory. Each one is a repository agents work in, with the team's rules for it.
- New project asks what you are making and whether it already exists, then the repository and a name; creating it starts the Repo Wizard's task.
- The integration branch is where agents start from and deliver into; the two gate commands are the checks every change must pass.
- Access is given under the project's Settings › Access, to a group with a role.
Next
Next lesson: Machines and capacity. Previous: Scheduled tasks.
Related: