
Oadp Rebase
- Updated June 9, 2026
- migtools/oadp-rebase-ai-helpers
oadp-rebase is a Claude Code skill in the Automation & Workflows category. OADP rebase workflows for rebasing upstream Velero ecosystem repos into OpenShift downstream forks
Key points
- oadp-rebase
- Automation & Workflows
- AI-coding skill
Oadp Rebase by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin marketplace add migtools/oadp-rebase-ai-helpers/plugin install oadp-rebase@oadp-rebase-ai-helpersAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Last updated | June 9, 2026 |
|---|---|
| Repository | migtools/oadp-rebase-ai-helpers ↗ |
What it does
OADP rebase workflows for rebasing upstream Velero ecosystem repos into OpenShift downstream forks
README.md
OADP Rebase Plugin
The OADP Rebase plugin provides Claude Code commands for automating the OADP (OpenShift API for Data Protection) rebase process. It handles rebasing ~20 downstream OpenShift forks of the Velero backup/restore ecosystem to newer upstream versions.
Commands
| Command | Description |
|---|---|
/oadp-rebase:rebase |
Run a full rebase for a single repo or entire wave |
/oadp-rebase:verify-commits |
Verify downstream carry commits are preserved |
/oadp-rebase:update-config |
Update config to target a new upstream version |
/oadp-rebase:manual-rebase |
Handle repos needing manual intervention |
/oadp-rebase:status |
Check rebase status across all repos |
/oadp-rebase:update-dependency |
Update go.mod replace directives manually |
Skills
| Skill | Description |
|---|---|
| rebase-workflow | Complete end-to-end rebase procedure |
| verify-commits | Detailed commit verification guide |
| manual-intervention | Manual fix procedures for common failures |
| hook-scripts | Reference for all post-rebase hook scripts |
Key Concepts
Rebasebot
A tool that automates cherry-picking downstream commits onto new upstream bases. Available as a container image or CLI binary.
Wave Ordering
Repositories are organized into 5 waves based on dependency ordering. Always rebase Wave 1 before Wave 2, etc.
Commit Conventions
UPSTREAM: <carry>- Downstream patches that MUST be preserved across every rebaseUPSTREAM: <drop>- Auto-generated by hook scripts, regenerated each rebase (safe to lose)
Two Rebase Patterns
- Full rebase (source != dest): Cherry-picks onto new upstream tag
- Hooks-only (source == dest): Just runs hook scripts to update dependencies
Prerequisites
- rebasebot CLI or container image
- GitHub App private keys for oadp-rebasebot
- oadp-rebase repository with config files
- gh CLI, Go toolchain