Installing on a repository
Dicast installs as a GitHub App, a GitLab application, or a Bitbucket app. Access is per repository and revocable at any time.
GitHub
Install from the sign-up flow or directly from the GitHub Marketplace listing. On the repository screen, choose Only select repositories for your first install — organisation-wide access can wait until you know whether you want it.
Permissions requested
| Permission | Level | Why |
|---|---|---|
| Contents | Read | Reading the diff and the surrounding code for context. |
| Pull requests | Read & write | Posting review comments and replying to commands. |
| Checks | Read & write | Publishing the review and merge-gate status checks. |
| Metadata | Read | Required by GitHub for any app. |
Dicast does not request workflow, packages, or write access to contents. It cannot push commits or merge.
Installing across an organisation
An organisation owner can install for all repositories at once. Reviews still only run where a repository is enabled in your Dicast workspace, so a broad install does not mean broad billing — see plans and quotas.
GitLab and Bitbucket
Available on Team and Scale. GitLab merge requests and Bitbucket pull requests support the same checks, comments and commands. Self-managed GitLab instances need the self-hosted runner.
Removing access
Uninstall from your provider’s settings, or disable the repository in your workspace. Removing access stops reviews immediately; the struck record for past pull requests is retained until your plan’s retention window elapses.