Skip to content

feat: add backport automation skills - #71

Open
lokanandaprabhu wants to merge 3 commits into
redhat-developer:mainfrom
lokanandaprabhu:new-skill-backport
Open

feat: add backport automation skills#71
lokanandaprabhu wants to merge 3 commits into
redhat-developer:mainfrom
lokanandaprabhu:new-skill-backport

Conversation

@lokanandaprabhu

Copy link
Copy Markdown
Member

Summary

  • Adds three backport skills to automate the RHDH plugin backport process (currently fully manual, inherited from backstage/community-plugins)
  • backport-auto — Fully automated end-to-end: detect plugin, reset workspace, cherry-pick (with AI conflict resolution), create sequential PRs, handle Version Packages, /publish + merge overlays, changelog PR
  • backport-create — Semi-manual: creates backport PRs and stops for user review
  • backport-finish — Completes the workflow after manual PR merges (Version Packages, overlays, changelog)

Files

  • skills/backport-auto/ — SKILL.md + README.md + 8 reference files
  • skills/backport-create/ — SKILL.md + README.md (reuses backport-auto references)
  • skills/backport-finish/ — SKILL.md + README.md (reuses backport-auto references)
  • README.md — Added Backport section

Known Gaps (pending team input)

1. Concurrent backport race condition

The workspace/{plugin} branch is shared across all releases. If two people backport the same plugin to different releases simultaneously (e.g., 1.9 and 1.10), the second workspace reset clobbers the first. Waiting for team guidance on approach (release-scoped branches, locking, etc.).

2. Branch pre-creation for new plugins/releases

workspace/{plugin} and {plugin}/release-x.y branches may not exist for new plugins or new release versions. Need clarification on whether the skill should create them or if they must be pre-created manually.

Test plan

  • Dry-run with an already-merged PR to validate detection and prerequisite logic
  • End-to-end test with a real backport PR once available
  • Validate /publish + metadata version mismatch fix flow on overlays repo

🤖 Generated with Claude Code

… backport-finish)

Three skills to automate the RHDH plugin backport process:

- backport-auto: Fully automated end-to-end backport workflow
- backport-create: Semi-manual — creates PRs and stops for review
- backport-finish: Completes workflow after manual PR merges

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
lokanandaprabhu and others added 2 commits July 30, 2026 11:11
Add stdlib-only Python script implementing the 13-step backport workflow.
SKILL.md files now invoke the script instead of listing individual commands,
keeping only conflict resolution logic in the agent layer.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Replace manual overlays clone/edit with GitHub Actions workflow trigger
  (update-plugins-repo-refs.yaml) for step 11
- Fetch source.json via GitHub API instead of cloning overlays repo (step 4)
- Fix --mode create help text (steps 1-7, not 1-8)
- Update SKILL.md files: remove overlays fork prerequisite, fix step
  descriptions for PR creation order and overlays workflow
- Rewrite overlays-update.md reference to document workflow-based approach
- Improve poll_publish_result to parse actual bot comment patterns

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant