Use Cases

recommit is designed for teams that maintain multiple versions of their software simultaneously. Here are the most common use cases.

Who Benefits from recommit?

Open Source Library Maintainers

If you maintain a library with multiple major versions (v1, v2, v3), you know the pain of:

• Backporting bug fixes to all versions
• Ensuring security patches reach all supported releases
• Keeping documentation in sync

→ Library Versioning Guide

Enterprise Product Teams

B2B software companies often need to:

• Support multiple product versions for different customers
• Maintain LTS (Long Term Support) branches
• Deploy hotfixes across all active releases

→ Enterprise Releases Guide

Security Teams

When a vulnerability is discovered, you need to:

• Patch all affected versions quickly
• Ensure no supported version is left vulnerable
• Track that all branches received the fix

→ Security Patches Guide

Common Scenarios

Before recommit

# The old way - for every PR merged to main
git checkout v3
git cherry-pick abc123
git push origin v3
 
git checkout v2  
git cherry-pick abc123
# Conflict! Spend time resolving...
git push origin v2
 
git checkout v1
git cherry-pick abc123
git push origin v1
 
# Repeat for every PR, every day...

After recommit

1. Merge PR to main
2. ✅ Done - recommit handles the rest

Quick Comparison

Getting Started

Choose the guide that matches your situation:

• Library Versioning - Open source or internal libraries
• Enterprise Releases - Multi-version SaaS or on-prem products
• Security Patches - Rapid vulnerability response