Pipeline: Find the readme and contents overlays where the toolbox now keeps them - #154
Merged
Merged
Conversation
The toolbox folds code/internal into code/+openminds and moves the readme and contents overlays to code/resources. The apply script still looked for them under code/internal/resources, where it would find nothing and stop before restoring them. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
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.
Merge after #135, not before.
That PR folds
code/internalintocode/+openmindsand moves the readme and contents overlays fromcode/internal/resourcestocode/resources. The apply script still looks for them at the old path, where it would find nothing, report the missing overlay and stop before restoring them. The generated classes would land, and everyREADME.mdandContents.mthat lives among them would not.Only the overlay location changes.
code/generated/resources, which the same script writes to, is unaffected by that move.Until #135 merges this PR is the wrong way round, so it should sit until then.
🤖 Generated with Claude Code