Connect GitHub
FlawDesk keeps a project's code in a GitHub repository. From there it clones to your server, pushes go there, and it is the basis for the links between tickets and commits.
1. Choose the access method
Under Project settings → FlawDesk Code → Source there are three ways:
| Way | When |
|---|---|
| FlawDesk App (recommended) | You install the FlawDesk app in your GitHub account or organisation. Commits run as flawdesk[bot], credentials renew automatically, rights are limited to what is needed. |
| My GitHub account | You sign in once via GitHub login. For repositories in your personal account. Commits run under your name. |
| Personal access token (legacy) | Manual fallback when the other two are not possible. You create and renew the token yourself. |
2. Install the FlawDesk App
The installation happens once per GitHub account or organisation, not per project:
1. Gear icon at the bottom of the sidebar → Settings → GitHub tab. 2. Click Install FlawDesk App. You are redirected to GitHub. 3. On GitHub you choose where the app is installed (your account or an organisation) and which repositories it may access — all or selected. Confirm. 4. GitHub redirects you back; the installation appears in the list. Via Manage on GitHub you can later add repositories or remove the app.
3. Link the repository
Back in the project, Source → FlawDesk App:
1. Account — pick the installation (if you have several). 2. Repository — pick an existing one from the list.
Or + Create new repo: FlawDesk creates it directly on GitHub. This only works in organisations; a new repository in your personal account is created via "My GitHub account". 3. Optionally set the default branch (otherwise main). 4. Save.
4. Clone or initially fill the repository
The repository is linked but not yet on your server. Open the Filetree view in the left rail:
- Repository already has content → Clone repo now, pick the branch, confirm. FlawDesk clones into the workspace path you entered when connecting the server.
- Repository is empty (freshly created) → Initial push. FlawDesk creates a starter skeleton, commits it and pushes to GitHub. After that the workspace on the server exists.
Both can only be triggered by the workspace owner.
From here on you see the files on the server in the Filetree, can view and edit them, and an AI client with a connector works in the same directory.
Common problems
"Repo access failed" — The app has no rights on this repository (see the warning above) or the repository was renamed. If in doubt, select it again under Source.
Cloning aborts — Usually git is missing on the server or the SSH user has no write access in the workspace path. Server status → Check now shows it.
Commits appear as flawdesk[bot] — This is intended with the FlawDesk App: it is visible what came through FlawDesk and what was done by hand. If you want commits under your own name, use "My GitHub account".