Git comment

Node catalog Actions

On this page

Comments on an issue or pull request

Usage and specifics

number identifies the target issue or pull request; target distinguishes the resource type. The token must permit adding comments.

Technical type : git_comment. 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
`number`	`number`	`""`	-; > 0
`target`	`enum`	`"issue"`	`issue`, `pull_request`
`body`	`string`	`""`	-; min 1

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.
target Comment target: Choose issue or pull request to select the correct GitLab endpoint.
number Issue or pull request number: Repository number, without prefix.
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": "",
  "number": "",
  "target": "issue",
  "body": ""
}

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.