GitLab API icon

GitLab API

Gitlab
Join our community

Actions880

Overview

This node operation performs a POST request to the GitLab API endpoint `/api/v4/topics/merge` to merge topics. It is useful in scenarios where you want to consolidate multiple topics into a single one within a GitLab instance, helping to organize and manage topics more efficiently.

Use Case Examples

  1. Merging two or more GitLab topics into one to reduce redundancy.
  2. Automating topic management in GitLab projects by merging outdated or duplicate topics.

Properties

Name Meaning
Skip Authentication Determines whether to skip authentication for the request.
Authentication Specifies the authentication method to use, typically an API key credential for GitLab.
baseUrl The base URL of the GitLab instance to which the request is sent.
Method The HTTP method used for the request, defaulting to POST for this operation.
Parameter Schema Defines the schema for the request body parameters required to merge topics.
Request Body Schema Schema for the request body, typically containing the details of the topics to merge.
Request Path The API endpoint path `/api/v4/topics/merge` for merging topics.

Output

JSON

  • id - The ID of the merged topic.
  • name - The name of the merged topic.
  • description - The description of the merged topic.
  • created_at - Timestamp when the merged topic was created.
  • updated_at - Timestamp when the merged topic was last updated.

Dependencies

  • GitLab API authentication token or API key credential

Troubleshooting

  • Ensure the baseUrl is correctly set to your GitLab instance URL.
  • Verify that the authentication token or API key has sufficient permissions to merge topics.
  • Check that the request body conforms to the required schema for merging topics.
  • Common errors include authentication failures, invalid request body format, or insufficient permissions.

Links

Discussion