Repository navigation
fix(validate): fetch scripts from molecule-ci instead of vendored copy - #24
Merged
Merged
Conversation
…pecting them in caller The validate-org-template.yml and validate-plugin.yml workflows expected `.molecule-ci/scripts/` to be vendored INTO each calling repo. That worked for the repos that copied the directory in, but broke on the ones that didn't: - molecule-ai-org-template-medo-smoke - molecule-ai-org-template-molecule-worker-gemini - molecule-ai-org-template-reno-stars - molecule-ai-plugin-molecule-compliance - molecule-ai-plugin-molecule-freeze-scope - molecule-ai-plugin-molecule-prompt-watchdog Surfaced when the secret-scan rollout PRs hit those repos and the required validate check failed on missing `.molecule-ci/scripts/requirements.txt`. Mirror the same fix already in validate-workspace-template.yml: a second `actions/checkout@v4` of molecule-ci into `.molecule-ci-canonical/`, with script paths re-pointed accordingly. Single source of truth — callers never need to vendor or sync. Also adds `.molecule-ci-canonical` to the secret-scan SKIP_DIRS so the side-checked-out tree doesn't get walked. Callers can drop their vendored `.molecule-ci/scripts/` copies in a follow-up cleanup. Both shapes work after this PR — the vendored copy is harmless dead weight, not a conflict. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced Apr 29, 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
1 participant
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
`validate-org-template.yml` and `validate-plugin.yml` expected `.molecule-ci/scripts/` to be vendored into the calling repo. That broke when callers didn't have the directory.
This PR: mirror the fix already in `validate-workspace-template.yml` — a second `actions/checkout@v4` of molecule-ci into `.molecule-ci-canonical/`, re-point script paths.
Currently broken (will be fixed by this PR)
All 6 are stuck on `validate / Org template validation` (or `/ Plugin validation`) failing with: `No file in [...] matched to [.molecule-ci/scripts/requirements.txt or **/pyproject.toml]`.
Changes
Verification
🤖 Generated with Claude Code