The repository is yours. ingestia writes the definitions to it (never data, never
credentials) inside one folder (ingestia/ by default) and does not touch the rest.
Connect (recommended)#
In ETL/ELT → CI/CD → Git repository, click Connect with GitHub, Connect with GitLab or Connect with Azure DevOps. You sign in to your account, authorize ingestia and come back to pick the repository from a list. No one copies a token:
- GitHub: you install the ingestia app only on the repositories you choose. On the GitHub screen, select Only select repositories and pick just the data repository. To change it later, use Grant access to more repositories on GitHub in the list; to remove access, uninstall the app in your GitHub account.
- GitLab: authorization of your gitlab.com account; access renews by itself.
- Azure DevOps: sign-in with the company's Microsoft account; access renews by itself.
When you pick the repository, ingestia checks access by itself. It only writes a first commit if the repository is empty; in a repository with content, nothing is written by the test.
Use a token (advanced)#
For a self-hosted server (GitHub Enterprise, self-managed GitLab) or automation, open Use a token (advanced) and follow the steps below.
1. Create a token for this repository only
See below how to do it in each provider.
2. Fill in the form
In ETL/ELT → CI/CD → Git repository: provider, Repository link (as it appears in the browser) and Access token. Use Save.
3. Test
Use Test. In an empty repository, the test writes the first file — it is the proof that ingestia can write.
Branches and sending#
- Production branch (default
main) receives the Production state. - Development branch (default
dev) receives the Development state. - Each send gets its own branch (
dev-envio-<n>), created from the Production branch; the change request comes from it and always merges cleanly. - When to write to Git: On every publication (default) or Only when I ask (button Send to Git now).
Token in each provider#
GitHub
In Settings → Developer settings → Personal access tokens → Fine-grained tokens: select only the repository and grant Contents: Read and write and Pull requests: Read and write (Metadata: Read comes with it).
GitLab
In the project, Settings → Access tokens: role Developer (or higher) and scope api. It also works on self-managed GitLab — choose GitLab and paste your server's link.
Azure DevOps
Azure DevOps is ready but has not yet been validated against a real repository. For production, prefer GitHub or GitLab.
In User settings → Personal access tokens: the repository's organization and scope
Code: Read & write. Paste the link in the format
https://dev.azure.com/<organization>/<project>/_git/<repository>.
If there is an error#
| Message | What to do |
|---|---|
| The provider rejected the token | Check the token is correct and not expired. |
| The token can only read | Grant write access to contents. |
| Repository not found | Check the link; a private repository needs a token with access to it. |
| The provider is rate-limiting calls | Wait a few minutes. |