Module · requires task boards
GitLab, Forgejo and Gitea issues on the board where the team works
Enclessa connects to GitLab.com, a self-managed GitLab, Forgejo or Gitea and mirrors a repository’s issues and merge or pull requests onto a task board as cards. Moving a card into the done column closes the issue it stands for, and moving it out reopens it; a card created on a board that files issues becomes a new issue. Writing back to the forge is a setting the organisation can switch off, and the connector never rewrites an issue’s own text.
Updated
- Hosts
- GitLab.com, self-managed GitLab, Forgejo and Gitea
- What syncs
- Issues and merge or pull requests, as board cards
- Done
- A card moved to done closes the issue; moved back, reopens it
- Write-back
- On by default, switched off per organisation
- Auth
- An access token and a webhook secret, stored sealed
- Requires
- The task boards module
How does the connection work?
An administrator connects the organisation to one forge at the address it lives at — GitLab.com, your own GitLab, a Forgejo or a Gitea — with an access token, and the forge’s webhooks tell Enclessa when something changes. A board is then linked to a repository, and its issues and merge or pull requests arrive as cards that stay in step with it.
- GitLab.com or a self-managed GitLab, Forgejo or Gitea, at an address you choose
- Credentials and the webhook secret encrypted before they are stored
- Each delivery re-read from the forge rather than trusted from its body
- A board linked to a repository, guarded by the permission that already governs boards
What does it write back?
Only the state the board owns. A card moved into or out of a done column closes or reopens what it mirrors, and a card created on a board that files issues becomes a new issue. Titles and descriptions on the forge are never rewritten. An organisation that wants the board to read and never write switches write-back off.
- Done closes the issue, and leaving done reopens it
- A new card can be filed as a new issue
- The issue’s own text is never rewritten
- Write-back is a per-organisation setting, on by default
What it does not do
Stated here rather than discovered after signing up.
- The connector requires the task boards module, because what it syncs are board cards.
- Bitbucket and Azure DevOps are not supported. GitHub has its own connector.
- Enclessa does not host code, run pipelines or review diffs. Pipeline status and review state are not shown on the card the way GitHub’s check results are.
- Write-back covers open and closed state and new issues. It is not a general-purpose editor for the forge.
Related
Questions
GitLab, Forgejo and Gitea: common questions
- Yes. The GitLab and Forgejo module mirrors issues and merge requests from GitLab.com or a self-managed GitLab onto an Enclessa task board, and moving a card to done closes the issue.
- Yes. The same module connects to Forgejo and Gitea at whatever address they run on, and mirrors their issues and pull requests onto a task board.
- Yes. Write-back is a per-organisation setting. It is on by default; with it off, the board reads from the forge and never writes to it.
Your team. Your keys. Your continent.
Create an organisation in a minute. Free for up to 10 active members, forever.