96864263bb
This repo is now a publish artifact of Molecule-AI/molecule-core/workspace/. Runtime code edits go to the monorepo; the publish-runtime workflow regenerates this mirror + uploads to PyPI on every runtime-v* tag. Changes: - Delete .github/workflows/publish.yml. PyPI publishing now happens only from the monorepo's publish-runtime workflow. Without removing this, two different code shapes could reach PyPI depending on which workflow fired (the drift this lockdown is preventing). - Delete .github/workflows/auto-promote-staging.yml. The staging→main fast-forward dance has no purpose on a mirror repo — the mirror is rebuilt wholesale on each release. - Replace .github/workflows/ci.yml with a 'mirror-guard' job that fails on any pull_request event with a clear redirect message. Push events are still allowed (so existing in-flight branches don't all turn red while the migration finishes); that allowance becomes a follow-up removal once the auto-sync from monorepo is wired up. - Rewrite README.md with a prominent ⚠ banner pointing at the monorepo. - Add CONTRIBUTING.md with the explicit redirect table. What this does NOT do: - Wire up the auto-sync from monorepo → this repo. The publish-runtime workflow currently uploads to PyPI but doesn't push the rewritten tree back here. As a follow-up, extend that workflow with a step that commits the build dir to this repo's main. Until then this repo's contents will go stale relative to PyPI — but that's fine because no one should be reading code from here anyway. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
1010 B
1010 B
Contributing
This repo is a publish artifact, not the source of truth.
Runtime code lives in Molecule-AI/molecule-core
under the workspace/ directory. This repo is regenerated by the
publish-runtime workflow on every runtime-v* tag.
Where to send your change
| Want to … | Open PR against … |
|---|---|
| Add a new tool | Molecule-AI/molecule-core → workspace/builtin_tools/ |
| Fix a bug in the runtime | Molecule-AI/molecule-core → workspace/ |
| Add a new adapter | Molecule-AI/molecule-ai-workspace-template-<runtime> (separate repo per adapter) |
| Update this README or CONTRIBUTING | Molecule-AI/molecule-core → workspace-runtime-readme.md (sync-published from there) |
What if you really need to edit this repo
You don't. Even hot-fixes go through the monorepo. If the monorepo path
is broken for some reason and you genuinely cannot wait, ping #platform
and an admin can override the mirror-guard CI.