docs: align runbook + known-issues with molecule-core local-build flow (followup to molecule-core #63) #5
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Followup to molecule-core Issue #63 / Task #194 (PR landing 2026-05-07).
What changed in molecule-core
When
MOLECULE_IMAGE_REGISTRYis unset, the workspace-server provisioner now clones THIS template repo from Gitea anddocker builds it locally instead of attempting the (post-suspension 403) GHCR pull. Seemolecule-core/docs/adr/ADR-002-local-build-mode-via-registry-presence.mdfor the full design.Doc updates needed in this repo
runbooks/local-dev-setup.mdStep 1Replace the GitHub clone URL (currently 403 on the suspended org) with the Gitea canonical URL:
Add a note that explains: when the contributor is running
molecule-corelocally withMOLECULE_IMAGE_REGISTRYunset, the provisioner clones this repo automatically — manual cloning is only needed when modifying template code itself.known-issues.mdAppend §5 documenting the post-2026-05-06 image-source flow:
molecule-ai/workspace-template-*(org suspended)MOLECULE_IMAGE_REGISTRYis unsetMOLECULE_IMAGE_REGISTRYpoints at ECR)docs/development/local-development.mdand ADR-002Draft text is in molecule-core PR description. Copy verbatim from there once that PR is merged.
Why this is a separate issue
The local copy of this template repo on the implementing agent's host (
~/molecules-org/.../) is a gitignored sandbox per the saved memoryfeedback_workspace_template_sandbox_is_stale— itsoriginstill points at the suspended GitHub URL. PRs against this Gitea repo need to be opened from a fresh Gitea-origin clone. Filing as a doc-only follow-up.Acceptance criteria