Actions26
Overview
The node "Git Extended" allows users to run a wide range of Git commands programmatically within an n8n workflow. It supports operations such as cloning repositories, committing changes, pushing and pulling branches, managing branches and tags, applying patches, configuring user identity, and more.
This node is beneficial in automation scenarios where Git repository management needs to be integrated into workflows without manual intervention. For example:
- Automatically committing and pushing code changes after a build or test step.
- Cloning repositories and checking out specific branches for deployment pipelines.
- Managing branches and tags as part of release automation.
- Configuring Git user identity dynamically before commits in multi-user environments.
Specifically, the Configure User operation sets the Git user name and email configuration for commits in a given repository path.
Properties
| Name | Meaning |
|---|---|
| Repository Path | Filesystem path to run the Git command from. For clone, the repository will be created inside this path. |
| User Name | User name for commits (required for Configure User operation). |
| User Email | User email for commits (required for Configure User operation). |
| Skip Stdout | Whether to ignore command output to avoid maxBuffer errors. |
Output
The node outputs JSON data containing the standard output (stdout) and standard error (stderr) of the executed Git command unless Skip Stdout is enabled. In that case, the output JSON is empty.
For the Configure User operation, the output JSON will typically be empty because the command configures Git user settings silently. If there are errors, they will be thrown as exceptions or included in the error output if "Continue On Fail" is enabled.
No binary data output is produced by this node.
Example output JSON when not skipping stdout:
{
"stdout": "",
"stderr": ""
}
Dependencies
- Requires Git to be installed and accessible on the system where n8n runs.
- Uses Node.js child process execution to run Git commands.
- Requires an API key credential for authentication when performing operations like clone, push, and pull with authentication.
- No additional external services are required beyond Git and optional credentials for authenticated Git access.
Troubleshooting
Common issues:
- Git not installed or not in PATH: The node will fail to execute commands.
- Invalid repository path: Commands will fail if the specified path does not exist or is inaccessible.
- Authentication failures: When using authenticated operations, incorrect credentials or missing permissions can cause errors.
- Buffer overflow errors: Large command outputs may cause maxBuffer errors; enabling "Skip Stdout" can mitigate this.
Error messages:
Unsupported operation <operation>: The selected operation is not implemented or recognized.Command failed with exit code <code>: The Git command returned a non-zero exit status indicating failure.Failed to parse the repository URL: The provided repository URL is invalid or malformed.Commit ID is required: Required commit hash parameter is missing for operations like cherry-pick or revert.
Resolutions:
- Ensure Git is installed and accessible.
- Verify repository paths and URLs.
- Provide correct credentials for authenticated operations.
- Use "Skip Stdout" option to avoid buffer size issues.
- Check required parameters for each operation.