Git pull request

Node catalog Actions

On this page

Creates a pull request or merge request

Usage and specifics

Set repo, head and base. The references must exist on the provider; draft support depends on the provider.

Technical type : git_pull_request. 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
`repo`	`string`	`""`	-; min 1
`credentialId`	`string`	`""`	-; min 1
`title`	`string`	`""`	-; min 1
`body`	`string`	`""`	-
`head`	`string`	`""`	-; min 1
`base`	`string`	`"main"`	-; min 1
`draft`	`boolean`	`false`	-

Configuration help

repo Repository URL: HTTPS URL of a GitHub, GitLab or Gitea repository. Expressions supported.
credentialId Git credential: Git credential with an HTTPS token and repository write access. Push also accepts an SSH key.
title Title: Pull request or issue title. Expressions supported.
head Source branch: Branch containing the proposed changes.
base Target branch: Destination branch.
draft Draft: Create a draft pull request (GitHub and GitLab).
body Body: Body or comment text. Expressions supported.

Initial configuration

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

json

{
  "repo": "",
  "credentialId": "",
  "title": "",
  "body": "",
  "head": "",
  "base": "main",
  "draft": false
}

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.