Projects
A project is a GitHub repository with its own factory, deploy target, and knowledge base.
Each project is a workspace in the studio, built around one GitHub repository. Its tabs show the overview, the board of running tickets, the factory configuration, and settings.
Create a project
- Open New project and pick a repository the Appli Studio GitHub App can access.
- In Settings, choose the project's deploy target: a Dokploy application with preview deployments.
- On the Overview, work through the setup checks until they're green.
Planned
Creating a new repository from a template, and setting up the Dokploy application and knowledge base in the same flow.
Setup checks
The overview reads the repository and the deploy target live and shows what the factory still needs:
| Check | Why it matters | Fix |
|---|---|---|
| Labels | Agents and gates use ready, type:*, size:*, risk:*, and appli:* | Create labels in the studio |
| Setup recipe | .appli/setup.json tells the worker how to install and check the code | Add it to the default branch |
| GitHub App access | The app should reach only repositories with projects | Install it on selected repositories |
| Branch protection | Without it, a hand merge skips the gates | Require appli/checks, appli/review, and appli/qa |
| Production deploys | The deploy gate waits for production to run the merge | Turn on auto deploy for the default branch |
| Preview deployments | QA tests every pull request on its own preview | Turn on previews; allow the app's pull requests |
Members and roles
Owners invite people from Settings → Members. An invitation is a link that works once, for seven days; the person creates an account (or signs in) and joins with the role you chose.
| Role | Can |
|---|---|
| Owner | Everything, including connections, members, and configuration |
| PO / PM | View the project and its runs |
| Developer | View the project and its runs |
| Ops | View the project and its runs |
People can sign in with a password or with passkeys added on their account page.