docs: add multi-remote workflow — where issues/MPs belong across local, staging, production
Documents the internal-vs-external split now that MuseHub's own repos are going live on production: internal issues/MPs/merges always happen on staging, production is a deployment target plus the public surface where external contributors will file issues/MPs, and releases/tags are cut against production since that's the live, linkable environment.
sha256:b02a146114e3dfa75fac9b2df4d1a72d6a7bdf0413d73bcdb6871b61046d61c9
sha
+10
symbols
1 changed · 1060 in snapshot
files
sha256:5256f2a775d5817ed7a3522adfec08ca1cf028b704bad3791fec423cd6005783
snapshot
+10
symbols added
1
file changed
1060
files in snapshot
0
dead code introduced
Semantic Changes
10 symbols
+
.vscode/
+
alembic/
+
deploy/
+
docs/
+
musehub/
+
scripts/
+
src/
+
src/ts/
+
tests/
+
tools/
+
Multi-Remote Workflow — Local, Staging, Production
section Multi-Remote Workflow — Local, Staging, Production L1–126
+
Concrete example — bumping musehub's PATCH version
section Concrete example — bumping musehub's PATCH version L49–118
Files Changed
+1
1060 in snapshot
+1
1060 in snapshot
← Older
Oldest on docs/multi-remote-workflow
All commits
Newer →
Latest on docs/multi-remote-workflow
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:b02a146114e3dfa75fac9b2df4d1a72d6a7bdf0413d73bcdb6871b61046d61c9 --body "your comment"
No comments yet. Be the first to start the discussion.