Git push

Node catalog Actions

On this page

Pushes the workspace commit to a remote branch

Usage and specifics

The workspace must already contain a repository and the commit to push. The token or SSH key must permit writes to the remote branch.

Technical type : git_push. Runtime : nodulz.

Credentials and prerequisites

Create and configure the credential : git

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter	Type	Default	Values / limits
`workspaceSource`	`union`	`{"kind":"upstream"}`	-
`workspaceSource.kind`	`literal`	`"upstream"`	`upstream`, `node`
`workspaceSource.key`	`string`	-	-; min 1
`credentialId`	`string`	`""`	-; min 1
`branch`	`string`	`""`	-

Configuration help

branch Branch: Remote branch to update. Empty: checkout branch.
credentialId Git credential: Git credential with an HTTPS token and repository write access. Push also accepts an SSH key.

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json

{
  "workspaceSource": {
    "kind": "upstream"
  },
  "credentialId": "",
  "branch": ""
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.