sloanops.admin/3031023-xyz-public
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify CMS back-sync boundary

Browse Source
This commit is contained in:
Kevin
2026-09-04 22:30:00 -04:00
parent e42d281b9a
commit 2f48055ce7
3 changed files with 12 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+3 -2
View File
@@ -33,8 +33,9 @@ branch; it never writes to `main`.
4. Merge only after the required CMS validation, both site builds, and SloanOps
review pass.
5. Relevant `main` changes deploy the production primary and/or blog Worker.
6. Synchronize the resulting `main` merge commit back into `cms` through a
protected-branch pull request before the next editing cycle.
6. If `main` contains file changes that are not already in `cms`, synchronize
them back through a protected-branch pull request before the next editing
cycle. A merge commit whose tree already matches `cms` needs no no-op sync.
Operator-authored CMS application or configuration work also starts from the
current `cms` state. Use a short branch and a pull request into protected