Skip to content

Pipeline: Find the readme and contents overlays where the toolbox now keeps them - #154

Merged
ehennestad merged 1 commit into
pipelinefrom
follow-overlay-move-out-of-internal
Sep 6, 2026
Merged

ehennestad merged 1 commit into
pipelinefrom
follow-overlay-move-out-of-internal

Conversation

@ehennestad

Copy link
Copy Markdown
Collaborator

Merge after #135, not before.

That PR folds code/internal into code/+openminds and moves the readme and contents overlays from code/internal/resources to code/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 every README.md and Contents.m that 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

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>
@ehennestad
ehennestad merged commit 8f9eeda into pipeline Sep 6, 2026
@ehennestad
ehennestad deleted the follow-overlay-move-out-of-internal branch September 6, 2026 18:23
@ehennestad ehennestad changed the title Find the readme and contents overlays where the toolbox now keeps them Pipeline: Find the readme and contents overlays where the toolbox now keeps them Sep 6, 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.

1 participant