Documentation Index

Fetch the complete documentation index at: https://docs.darwinium.com/llms.txt

Use this file to discover all available pages before exploring further.

Repository Access

  • Updated on Jun 23, 2026
  • Published on Jan 17, 2024
  • 1 minute(s) read
  • MB
 Prev Next

Darwinium provides the ability for users with appropriate privileges to clone the Workflows git repository.
(Where Journeys, Features, Rules are configured).

Workflows read access required

The user will need at least Workflows read access in order to clone a node's git repository

1. Generate SSH key

Cloning the repository will require an SSH key.

Can refer to public docs for creating and managing SSH Keys:
https://docs.github.com/en/authentication/connecting-to-github-with-ssh

2. Upload key to Darwinium Portal

Navigate to Git Access settings:
Darwinium Portal > Name > Preferences > Git Access
Screenshot 2025-11-25 at 10.13.29.png
and add your public SSH key made in previous process

3. Clone the repository

Below in the same screen Git Access screen will give the URLs of the node repositories that you have access to clone.
Screenshot 2025-11-25 at 10.15.54.png

Example: The URL will have your organization name and node-domain (two random words assigned to the node).

git clone ssh://git@git.darwinium.com:1904/exampleorg/example-node.git

The repository is now cloned, with the remote being the Node's repository.

Editing outside Darwinium removes config validation

Cloning and editing a repository outside the Darwinium Portal environment means no longer having useful syntax and pre-commit build validation.

Pushing a commit into master branch will still initiate build validation process, but you may encounter build failures that would otherwise be caught from editing within Darwinium Workflows directly.