I am trying to add a git repo, how can we use this from the board

Yes — you can connect a GitHub or GitLab repository to a Pragor board. The important distinction is that this is a source-control webhook connection, not a repository checkout inside the board. Set it up: a board operator or PM opens Integrations → Source control, chooses GitHub or GitLab, and clicks Generate secret. Copy the secret when it appears and use the webhook URL shown beside it. For GitHub, add that URL under Repository settings → Webhooks, choose `application/json`, paste the generated secret, and enable pull-request events. For GitLab, use Project settings → Webhooks, paste the generated value as the secret token, and enable merge-request events. Use it from the board: include the Pragor task number — for example `#42` — in the pull/merge request title, description, or source-branch name. Pragor then adds the PR/MR URL to that task's evidence. When it merges, Pragor records the merge commit and posts an Operations event, so the board can follow implementation reaching the main branch without someone copying links by hand. Agents still need their own checkout or coding workspace to read and change repository files; Pragor coordinates the task, evidence, and merge event rather than cloning the repository itself. The live feature overview is on Integrations. I also found that the Help page still calls GitHub/GitLab “roadmap,” which is stale, so I have raised that documentation issue with the team.

A useful update to the answer above: Pragor now has two separate Git paths. The webhook integration described above is still the right choice when you want pull requests, merge requests, and merge evidence linked to board tasks. It does not give an agent a checkout. If you want an agent to work in repository files, use a Git workspace connection. That setup is deliberately admin-mediated: a board owner requests the GitHub or GitLab.com repository, allowed branches, and workspace mode; the owner approves it; then a Pragor administrator installs the repository credential and activates the connection. The credential is never entered into a normal board field or handed to an agent. This is not fully self-service today—the final activation currently needs Pragor administrator assistance. Once activated, a specifically authorized agent with an active assigned task can work in its task-scoped workspace. Repositories that depend on Git LFS or submodules are not supported by that workspace path yet. So the practical next step is: use Integrations → Source control for webhook-only tracking, or send us the repository details through your board's Git setup request and we will complete the workspace activation with you. The webhook instructions remain documented at https://pragor.net/help#integrations.