Enable Repository
Enabling a repository activates automatic cherry-picking. When a PR is merged, recommit will automatically cherry-pick the changes to all branches defined in the linked roadmap.
Prerequisites
Before enabling a repository, ensure:
- ✅ Repository is imported (via GitHub App installation)
- ✅ A Roadmap has been created
- ✅ Repository is linked to the Roadmap
- ✅ Your organization has an active subscription
How to Enable
Open Repository Settings
- Go to Console → Repositories
- Find and click on the repository you want to enable
Link a Roadmap (if not already linked)
If the repository doesn't have a roadmap linked:
- Click the Roadmap dropdown
- Select the appropriate roadmap
- The link is saved automatically
Toggle Enable Switch
- Find the Enable toggle switch
- Click to turn it ON
- The repository is now active
What Happens When Enabled
Once enabled, recommit will:
- Listen for PR events via GitHub webhooks
- Detect merged PRs on any branch
- Execute cherry-picks to all roadmap branches
- Create new PRs on each target branch
Only merged PRs trigger cherry-picks. Closed (unmerged) PRs are ignored.
Disabling a Repository
To temporarily stop auto cherry-picking:
- Go to Console → Repositories
- Click on the repository
- Toggle Enable to OFF
When disabled:
- No new cherry-picks will be triggered
- Existing in-progress cherry-picks will complete
- Historical records are preserved
- You can re-enable anytime
Common Use Cases
Temporary Pause
Need to pause cherry-picks during a release freeze?
- Disable the repository
- Complete your release process
- Re-enable when ready
Testing Configuration
Want to test your roadmap setup safely?
- Create a test branch
- Enable the repository
- Merge a small test PR
- Verify cherry-picks worked correctly
- Adjust roadmap if needed
Emergency Stop
If cherry-picks are causing issues:
- Disable the repository immediately
- Investigate the problem
- Fix any conflicts or misconfigurations
- Re-enable when resolved
Troubleshooting
Repository Won't Enable
Check these common issues:
| Issue | Solution |
|---|---|
| No roadmap linked | Link a roadmap first |
| Subscription expired | Renew your subscription |
| GitHub App suspended | Check GitHub App settings |
Enabled But No Cherry-Picks
Verify the following:
- PR was merged (not just closed)
- Target branch exists in roadmap
- Repository status is "Normal"
- Check Cherry-Pick History for errors
Status Shows "Suspended"
This means the GitHub App access was suspended:
- Go to GitHub → Settings → Applications
- Find recommit app
- Check if it's suspended
- Re-authorize if needed
Best Practices
Start with Test Repos
Before enabling important repositories:
- Test with a less critical repository
- Verify the workflow works as expected
- Then enable production repositories
Monitor Initial Cherry-Picks
After enabling:
- Merge a test PR
- Watch the cherry-pick history
- Verify PRs are created correctly
Keep Roadmap Updated
Regularly review your roadmap:
- Remove end-of-life branches
- Add new release branches
- Update branch order if priorities change