This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
GitLab MR Actions
GitLab MR automation: auto-merge, rebase & Jira integration
Chrome extension that automates GitLab merge request workflows. One-click rebase, auto-merge, and version bump — chained into a single "Ship" button. Deep Jira integration: ticket status badges and detail sidebar right on MR pages. MR list enhancements: size labels, conflict warnings, unresolved threads, approval badges, branch names. Cherry-pick to multiple branches. Command palette (Cmd+K). Daily activity reports. Works with self-hosted GitLab — no API tokens, uses session cookies.
I built GitLab MR Actions to eliminate the repetitive manual work around GitLab merge requests that was slowing down my team every day.
Now it's one click. The "Ship" button chains rebase, version bump, and auto-merge automatically. Plus Jira ticket statuses show up as badges right on MR pages - no API tokens needed, just your session cookies.
Other highlights: MR size labels, conflict warnings, unresolved threads count, cherry-pick to multiple branches, command palette (Cmd+K), and daily activity reports. Works with any self-hosted GitLab. Free, open-source, 7 languages.
Would love your feedback - what GitLab pain points should I tackle next?
About GitLab MR Actions on Product Hunt
“GitLab MR automation: auto-merge, rebase & Jira integration”
GitLab MR Actions was submitted on Product Hunt and earned 4 upvotes and 1 comments, placing #127 on the daily leaderboard. Chrome extension that automates GitLab merge request workflows. One-click rebase, auto-merge, and version bump — chained into a single "Ship" button. Deep Jira integration: ticket status badges and detail sidebar right on MR pages. MR list enhancements: size labels, conflict warnings, unresolved threads, approval badges, branch names. Cherry-pick to multiple branches. Command palette (Cmd+K). Daily activity reports. Works with self-hosted GitLab — no API tokens, uses session cookies.
On the analytics side, GitLab MR Actions competes within Chrome Extensions, Open Source, Developer Tools and GitHub — topics that collectively have 676.4k followers on Product Hunt. The dashboard above tracks how GitLab MR Actions performed against the three products that launched closest to it on the same day.
Who hunted GitLab MR Actions?
GitLab MR Actions was hunted by Roman Termyanen. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of GitLab MR Actions including community comment highlights and product details, visit the product overview.
Roman Termyanen
I built GitLab MR Actions to eliminate the repetitive manual work around GitLab merge requests that was slowing down my team every day.
Now it's one click. The "Ship" button chains rebase, version bump, and auto-merge automatically. Plus Jira ticket statuses show up as badges right on MR pages - no API tokens needed, just your session cookies.
Other highlights: MR size labels, conflict warnings, unresolved threads count, cherry-pick to multiple branches, command palette (Cmd+K), and daily activity reports. Works with any self-hosted GitLab. Free, open-source, 7 languages.
Would love your feedback - what GitLab pain points should I tackle next?