Block 1 - Commit Message Breakdown
- Type / Role
- n8n-nodes-base.code - code
- Config choices
- Version 2
This workflow is provided as-is. Please review and test before using in production.
This n8n template from Intuz delivers a complete and automated solution to streamline your development workflow for a single repository. By embedding specific keywords and...
n8n-nodes-base.code, n8n-nodes-base.if, n8n-nodes-base.httprequest, n8n-nodes-base.githubtrigger, n8n-nodes-base.stopanderror, n8n-nodes-base.jira, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Intuz .
Original n8n.io sourceBy embedding specific keywords and a JIRA issue ID within your git commit commands, this workflow automatically creates a Pull Request in GitHub and simultaneously updates the corresponding JIRA ticket. This provides a complete, seamless integration that eliminates manual steps and keeps your project management perfectly in sync with your codebase.
This workflow acts as a powerful bridge between your Git repository and your project management tools, driven entirely by the structure of your commit messages.
GitHub Webhook Trigger: The workflow starts when a developer pushes a new commit to a specified repository in GitHub.
Parse Commit Message: A Code node extracts key information from the commit message:
Click the "Use Template" button to import this workflow into your n8n instance.
Configure the GitHub Trigger:
git commit -m "FF-1196 Implement OAuth login [auto-pr,development,taskcompleted]"
Click here- Get Started
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Automate GitHub PRs & JIRA updates from Git commit commands-single repo |
|---|---|
| Complexity | advanced |
| Nodes | 21 |
| Categories | DevOps |
| Author | Intuz |
| Published | 01 Aug 2025 |
Use the JSON export at /data/workflows/6773/6773.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
This n8n template from Intuz delivers a complete and automated solution to streamline your development workflow for a single repository. By embedding specific keywords and...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your DevOps use case.