Skip to content

Add claude slash command for upstream to downstream sync#750

Open
hroyrh wants to merge 1 commit into
openshift:mainfrom
hroyrh:merge-upstream-slash-command
Open

Add claude slash command for upstream to downstream sync#750
hroyrh wants to merge 1 commit into
openshift:mainfrom
hroyrh:merge-upstream-slash-command

Conversation

@hroyrh
Copy link
Copy Markdown

@hroyrh hroyrh commented Dec 18, 2025

No description provided.

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Dec 18, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: hroyrh
Once this PR has been reviewed and has the lgtm label, please assign derekhiggins for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Comment thread .claude/commands/merge-upstream.md Outdated

# Merging upstream to downstream

This commands merges changes from upstream `metal3-io/ironic-image`
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: command

Comment thread .claude/commands/merge-upstream.md Outdated

### 3. Handle Common Conflicts

**GitHub Workflows**: Downstream removes most of `.github/` directory files.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we do have .github downstream, we need to preserve what we have downstream

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, that's why it's most not all the files are removed, and the command below will not return empty if it makes any changes to the downstream files. I'm trying to avoid instructions for individual files, and trying to follow a consistent pattern where possible.

Comment thread .claude/commands/merge-upstream.md Outdated
- Verify with `git diff downstream/main -- .github/`, this must return empty
- If the above command result it not empty investigate or repeat above steps

**Hack tools**: We don't have these scripts in downstream normally:
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is upstream only

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, I will be more explicit in instructions here.

- `OCPBUGS-*:` - OpenShift bug fixes
- These must be preserved during the merge, unless replaced by an equivalent
upstream commit.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should probably add that Dockerfile is upstream and Dockerfile.ocp is downstream and find a way to apply the changes downstream

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I think Dockerfile, prepare-image.sh are candidates for bit for nuanced instructions. I've been trying different things with claude with some of these more complex scenarios, and it hasn't been very reliable on what it does. The more complex the instructions, the more it behaves unexpectedly. I will try to come up with more clear instructions.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for now we can just say to remove the Dockerfile from upstream and leave Dockerfile.ocp for downstream
but it will be on us to compare the changes

Comment thread .claude/commands/merge-upstream.md Outdated

### 5. Handling other conflicts

**OKD packages list**: Always pick the upstream changes for the okd packages
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there is no upstream OKD
I think we need to mention main-packages-list.txt and that we don't want to keep it downstream
same for ironic-packages-list

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm, I wonder why I saw conflicts in the okd file then ? Let me take another look.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, if a new package is added to the upstream list, we manually bring it in the downstream lists if applicable ?

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

upstream we install all from source, downstream we have a mix between source and RPMs, so yes, unfortunately most changes are done manually downstream as we don't have a 1to1 correspondence
with s2i things are going to get better

@hroyrh hroyrh force-pushed the merge-upstream-slash-command branch from da910c6 to 2727983 Compare December 18, 2025 17:57
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Dec 18, 2025

@hroyrh: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-bot
Copy link
Copy Markdown

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 19, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Mar 19, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 39f29875-300c-44d7-9dc9-edd198c1d866

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@dtantsur dtantsur requested a review from elfosardo April 14, 2026 10:59
@hroyrh
Copy link
Copy Markdown
Author

hroyrh commented Apr 14, 2026

/remove-lifecycle stale

@openshift-ci openshift-ci Bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 14, 2026
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.

3 participants