Actions18
- Branch Actions
- File Actions
- Issue Actions
- Merge Request Actions
- Pipeline Actions
- Raw API Actions
Overview
The "GitLab Extended" node integrates with GitLab to manage various resources such as branches, pipelines, files, issues, merge requests, and raw API calls. Specifically, the Branch - Get Many operation lists multiple branches from a GitLab repository.
This operation is useful when you want to retrieve an overview of all branches in a project, for example:
- Displaying all active branches for review or reporting.
- Automating branch cleanup by listing branches that meet certain criteria.
- Synchronizing branch data with other tools or dashboards.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all branches or limit the number of results returned. |
| Limit | Maximum number of branches to return if "Return All" is false. Minimum value is 1. |
Output
The output is a JSON array where each item represents a branch object retrieved from GitLab. Each branch object typically includes details such as branch name, commit information, and protection status (depending on GitLab's API response).
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating with GitLab.
- The node expects configuration of the target project either by numeric project ID or by owner/name combination.
- Uses internal helper functions to make authenticated HTTP requests to GitLab's REST API.
Troubleshooting
Common Issues:
- Incorrect project identification (wrong project ID or owner/name) will cause API errors.
- Insufficient permissions for the API token may result in authorization errors.
- Setting "Limit" to zero or negative values will be rejected due to minimum value constraints.
Error Messages:
"Unknown resource: branch": Occurs if the resource parameter is incorrectly set; ensure "branch" is selected."The 'oldLine' parameter must be a non-negative number.": Not relevant for this operation but appears in other operations; ensure parameters are valid.- API errors related to authentication or permissions should be resolved by verifying the API key and its scopes.