Automate GitHub Release Tracking to GitLab Issues
detail.loadingPreview
This workflow automatically monitors a GitHub repository for new releases. If a new release is detected and no corresponding issue exists in a specified GitLab project, it creates one, ensuring your team is always informed about upstream updates.
About This Workflow
Stay on top of critical upstream updates with this robust n8n workflow. Designed for DevOps and development teams, it intelligently monitors your chosen GitHub repository for the latest software releases. On a scheduled basis, it compares the latest GitHub release against existing issues in your GitLab project. If a new release lacks a corresponding GitLab issue, the workflow automatically generates one, complete with the release's URL and detailed body. This eliminates manual tracking, reduces the risk of missed updates, and streamlines communication for integrating new versions or addressing changes.
Key Features
- Automated GitHub Release Monitoring: Periodically checks a specified GitHub repository for new releases.
- Conditional GitLab Issue Creation: Creates a new issue in GitLab only if a new GitHub release is found and no matching issue already exists.
- Rich Issue Content: Automatically populates the GitLab issue with the GitHub release tag, URL, and description.
- Scheduled Execution: Configurable cron trigger allows you to define how often the workflow checks for updates.
How To Use
- Configure the 'Cron' node: Set your desired schedule for how often the workflow should run (e.g., 'everyWeek').
- Configure the 'Get latest release' (GitHub) node: Select your GitHub credentials, and specify the 'Owner' and 'Repository' you wish to monitor.
- Configure the 'List issues' (GitLab) node: Select your GitLab credentials, and specify the 'Owner' and 'Repository' where you want to check for existing issues.
- Configure the 'Create issue' (GitLab) node: Ensure your GitLab credentials are selected, and specify the 'Owner' and 'Repository' where new issues should be created. The title and body are dynamically pulled from the GitHub release, but you can add specific 'Labels' or 'Assignee IDs' if needed.
- Activate the workflow: Once configured, activate the workflow to begin automated monitoring and issue creation.
Apps Used
Workflow JSON
{
"id": "29b55155-9097-4fa5-9025-27523cd7515a",
"name": "Automate GitHub Release Tracking to GitLab Issues",
"nodes": 20,
"category": "DevOps",
"status": "active",
"version": "1.0.0"
}Note: This is a sample preview. The full workflow JSON contains node configurations, credentials placeholders, and execution logic.
Get This Workflow
ID: 29b55155-9097...
About the Author
Crypto_Watcher
Web3 Developer
Automated trading bots and blockchain monitoring workflows.
Statistics
Related Workflows
Discover more workflows you might like
Effortless Bug Reporting: Slack Slash Command to Linear Issue
Streamline your bug reporting process by instantly creating Linear issues directly from Slack using a simple slash command. This workflow enhances team collaboration by providing immediate feedback and a structured approach to logging defects, saving valuable time for development and QA teams.
Automate Qualys Report Generation and Retrieval
Streamline your Qualys security reporting by automating the generation and retrieval of reports. This workflow ensures timely access to crucial security data without manual intervention.
Automated PR Merged QA Notifications
Streamline your QA process with this automated workflow that notifies your team upon successful Pull Request merges. Leverage AI and vector stores to enrich notifications and ensure seamless integration into your development pipeline.