GitlabTrigger Automate

This workflow is ideal for:

• Developers looking to automate the creation of documentation upon new releases in GitLab.
• Project Managers who need to ensure that release notes are consistently documented and accessible.
• DevOps Teams aiming to streamline their deployment processes and improve collaboration by integrating documentation directly with code releases.

This workflow addresses the challenge of maintaining up-to-date documentation in tandem with software releases. By automating the process of creating documentation in Outline whenever a new release is tagged in GitLab, it ensures that:

• Documentation is created promptly and accurately.
• Teams save time and reduce manual errors associated with documentation updates.
• Stakeholders have immediate access to relevant release information, enhancing communication and project tracking.

1. GitLab Trigger: The workflow begins with a manual trigger from GitLab, specifically set to capture tag_push events in the ci-test repository owned by tennox.
2. IF Node: The workflow checks if the event type is a release. If the condition is met, it proceeds to the next step.
3. HTTP Request: An HTTP POST request is sent to the Outline API to create a new document. The request includes:
   • Collection ID and Parent Document ID (placeholders to be filled).
   • The title of the document, formatted to include the release name.
   • The text body containing the release description and a link for more information.