Fix opal-plus sync: use mirror approach to avoid conflicts#893
Merged
EliMoshkovich merged 1 commit intomasterfrom Apr 6, 2026
Merged
Fix opal-plus sync: use mirror approach to avoid conflicts#893EliMoshkovich merged 1 commit intomasterfrom
EliMoshkovich merged 1 commit intomasterfrom
Conversation
The merge approach conflicts every time on files with opal-plus customizations (on_release.yml, client.py). Instead, mirror opal/master exactly onto public-master and let the PR reviewer preserve opal-plus customizations during merge review. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
✅ Deploy Preview for opal-docs canceled.
|
zeevmoney
approved these changes
Apr 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
public-masteris reset to exactly matchopal/masteron_release.ymlandclient.pybecause those files have opal-plus customizations--force-with-leasepush is safe since only CI writes topublic-masterfetch-depth: 0from opal checkout (not needed — we just reset to HEAD)Test plan
🤖 Generated with Claude Code