Repository Connections
Repository Connections let you connect an external Git repository (currently GitHub) and use a file in it as the source of truth for a Transformer Library. This means you can manage your reusable transformer code in your own repository, with your own review process, and have Fenergo stay in sync automatically.
Why connect a repository?
- Single source of truth – your transformer code lives in your repository.
- Automatic updates – when you push a change, the matching library is updated for you. See Automatic synchronization.
- Your workflow – use your existing branching, review and CI process.
Concepts & glossary
| Term | Description |
|---|---|
| Repository Connection | A stored connection to an external Git repository, used to source and synchronize transformer libraries. |
| Provider | The Git hosting service. Currently GitHub is supported. |
| Access token | A token that lets Fenergo read your repository. It is stored securely and never shown again after it is saved. |
| Webhook | A notification your repository sends to Fenergo when code is pushed, so libraries can update automatically. |
How a repository becomes a library
- Connect the repository on the Repositories page, providing the repository details and an access token.
- Create a library from a specific file in the repository. This produces a published library.
- Keep it in sync – when code is pushed, the library is updated automatically. You can also synchronize manually at any time.
Each connected repository maps to a single repository-managed library.
Your access token is stored securely and is never displayed again after you save it. If it ever needs to change, you can refresh it from the Repositories page.
Future providers
Today only GitHub is supported. The feature is designed so that additional Git providers (such as GitLab or Bitbucket) can be added in the future.
Guides
- Managing Repositories – connect, validate, refresh and disconnect repositories in Integrations Studio.
- Automatic synchronization – how pushes keep your libraries up to date.
- Webhook Security – how notifications from your repository are kept secure.
- Webhook IP Allow-Listing – the extra network-level layer that only accepts notifications from GitHub.
- GitHub Setup & Troubleshooting – end-to-end setup and common issues.
Permissions
The actions you can take depend on your Integration Flows permissions:
- Access – view connected repositories and webhook details, and validate a token.
- Edit – connect a repository, synchronize, and refresh a token.
- Delete – disconnect a repository.