GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

Overview

This node operation fetches the forks of a specific project from the GitLab API (v4). It is useful for users who want to retrieve information about all the forks of a given project, such as in scenarios where they need to analyze or manage project forks programmatically. For example, a developer might use this to list all forks of a repository to check contributions or synchronize changes.

Use Case Examples

  1. Retrieve all forks of a project by its ID to display in a dashboard.
  2. Fetch forks of a project filtered by visibility or sorted by creation date.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the request.
Authentication The authentication method used, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance to connect to, defaulting to https://gitlab.com.
Method The HTTP method to use for the request, defaulting to GET.
Query Parameters Various optional query parameters to filter and sort the forks list, such as order_by, sort, archived, visibility, search, owned, starred, membership, and pagination options.
Path Parameters The path parameter 'id' specifies the ID or URL-encoded path of the project whose forks are to be retrieved.

Output

JSON

  • id - The unique identifier of the forked project.
  • name - The name of the forked project.
  • path - The path of the forked project.
  • created_at - The creation date of the forked project.
  • updated_at - The last update date of the forked project.
  • visibility - The visibility level of the forked project (private, internal, public).
  • archived - Whether the forked project is archived.
  • owner - Information about the owner of the forked project.
  • forked_from_project - Details about the original project from which this project was forked.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the project ID or path provided in the path parameter is correct and accessible by the authenticated user.
  • Verify that the authentication credentials (API key) are valid and have sufficient permissions to access project forks.
  • Check the baseUrl if connecting to a self-hosted GitLab instance to ensure it is correct.
  • If filtering by query parameters, ensure the values conform to expected types and allowed enums to avoid API errors.

Links

Discussion