View Cherry-Pick History
Coming Soon — This feature is currently under development and not yet available. The documentation below describes the planned functionality.
The Cherry-Pick History shows all automated cherry-picks executed by recommit. Use it to monitor status, track results, and troubleshoot issues.
Accessing History
Navigate to Console → Repositories → Select a repository → Cherry-Pick History
Or view organization-wide history in Console → Cherry-Picks
History View
Each entry displays:
| Field | Description |
|---|---|
| Status | Current state (Pending, Processing, Success, Failed) |
| From Branch | Source branch (where PR was merged) |
| To Branches | Target branches for cherry-pick |
| Commit SHA | The cherry-picked commit |
| Original PR | Link to the merged PR |
| Created PRs | Links to auto-created PRs |
| Time | When the cherry-pick was triggered |
Status Indicators
| Status | Icon | Meaning |
|---|---|---|
| Pending | 🕐 | Queued, waiting to execute |
| Processing | 🔄 | Currently running |
| Success | ✅ | Completed successfully |
| Failed | ❌ | Error occurred |
Filtering History
Filter by:
- Repository - Show specific repo only
- Status - Show Success, Failed, etc.
- Date range - Recent or historical
- Roadmap - Filter by roadmap used
Understanding Entry Details
Click on any entry to see details:
Success Entry
Status: ✅ Success
From: feature/auth-fix
To: main, v3, v2, v1
SHA: abc1234
Original PR: #456
Created PRs:
- main: #457 ✅ Merged
- v3: #458 ✅ Merged
- v2: #459 ⏳ Open
- v1: #460 ⏳ OpenFailed Entry
Status: ❌ Failed
From: feature/breaking-change
To: main, v3, v2, v1
SHA: def5678
Original PR: #789
Error: Conflict in src/api.jsCommon Actions
View Original PR
Click the Original PR link to see:
- What changes were merged
- Who authored the PR
- Discussion and reviews
View Created PRs
Click individual PR links to:
- Check if they're merged
- Resolve conflicts if any
- Review the cherry-picked changes
Retry Failed Cherry-Pick
Currently, failed cherry-picks cannot be retried automatically. You'll need to manually cherry-pick or resolve conflicts.
For failed entries:
- Check the error reason
- Resolve any conflicts
- Manually create PR if needed
Monitoring Best Practices
Daily Check
Review cherry-pick history daily to:
- Ensure all cherry-picks succeeded
- Merge pending PRs promptly
- Catch failures early
Set Up Notifications
Watch for:
- Failed cherry-picks (may need manual intervention)
- Stuck processing tasks (possible issues)
- Backlog of pending tasks
Track Metrics
Monitor over time:
- Success rate
- Average processing time
- Common failure reasons
Troubleshooting from History
Many Failures
If you see frequent failures:
- Check branch divergence
- Review roadmap configuration
- Consider more frequent branch syncing
Tasks Stuck in Processing
If tasks stay "Processing" too long:
- Check if there are complex conflicts
- Verify GitHub API connectivity
- Contact support if persistent
Missing Cherry-Picks
If expected entries are missing:
- Verify repository is enabled
- Check roadmap is linked
- Confirm PR was merged (not just closed)
- Verify subscription is active
Exporting History
Export functionality is planned for a future release.
Data Retention
Cherry-pick history is retained:
- Active subscriptions: Indefinitely
- After subscription ends: 90 days