GitHub Permissions

Here is exactly what Ceetrix can and cannot access from GitHub today. If we ever need a wider permission, GitHub asks you to approve it first, and this page changes before it does.

What We Request

Repository metadataRead-only. The most minimal repository permission GitHub offers.

Email addressesRead-only. Your account email, so we know who you are across devices.

What We Can See

Repository nameTo identify which project you are working on

VisibilityWhether the repo is public or private

Primary languageThe main programming language detected by GitHub

TopicsTags you have applied to the repository

OwnerThe GitHub user or organisation that owns the repo

Email addressesThe addresses on your GitHub account. We read only the one GitHub marks primary and verified, and store that as your Ceetrix account address

What We Cannot See Today

Source codeWe have zero access to your files or commits

File contentsWe cannot read, download, or clone your code

Commit historyWe cannot see your diffs, branches, or commit messages

Issues & pull requestsWe cannot read or create issues or PRs

Actions & workflowsWe cannot see or trigger your CI/CD pipelines

Secrets & variablesWe cannot access repository or environment secrets

Branch protection rulesWe cannot see or modify your branch policies

Write operationsWe cannot modify anything in your repository

Why We Need These

When you sign up, Ceetrix verifies you have access to the repository you claim to manage. Repository metadata lets us confirm the repo exists and that your GitHub account has access to it — without ever seeing your code.

Your account address identifies you across the web app and the command line, so the same person is never split into two accounts. We take it from the address GitHub has already verified rather than asking you to type one and trust it. If your GitHub account has no primary verified address, we refuse the sign-in instead of guessing.

That is the whole of what the GitHub app can reach today. Nothing on this page can change without GitHub asking you to approve the new permission, and you can decline and keep the access you have now.