Credential type in nodulz : git:https_pat / git:ssh_key.
Create access
In GitHub, open Settings → Developer settings → Personal access tokens and create a token limited to required repositories and permissions. In GitLab, create a Personal access token in your profile. For SSH, add the public key to the provider and store the private key in nodulz.
Configure in nodulz
In your instance, open Credentials, select the type above, name the credential and complete these fields:
text
secret, passphrase
Save the credential, then select it on relevant nodes. URLs or parameters marked as node settings belong directly on that node.
Things to check
Cloning requires read access; push, issues and pull requests need corresponding permissions. Organization tokens may require approval or SSO authorization.
Verify an operation with expected permissions and data before publishing. Keep secrets out of logs and revoke them with the provider when no longer needed.
Credential type in nodulz :
git:https_pat / git:ssh_key.Create access
In GitHub, open Settings → Developer settings → Personal access tokens and create a token limited to required repositories and permissions. In GitLab, create a Personal access token in your profile. For SSH, add the public key to the provider and store the private key in nodulz.
Configure in nodulz
In your instance, open Credentials, select the type above, name the credential and complete these fields:
Save the credential, then select it on relevant nodes. URLs or parameters marked as node settings belong directly on that node.
Things to check
Cloning requires read access; push, issues and pull requests need corresponding permissions. Organization tokens may require approval or SSO authorization.
Verify an operation with expected permissions and data before publishing. Keep secrets out of logs and revoke them with the provider when no longer needed.
Official references
See also : Credentials and rotation, Node catalog.