chris.dumas/holiday-property-booking
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: add operating cadence and clean styling
Some checks failed
Deploy Holiday Property Booking / deploy (push) Failing after 30s
Details
Playwright Holiday Property Booking / playwright (push) Failing after 6m57s
Details
Test & Build Holiday Property Booking / test-build (push) Successful in 10m43s
Details

Browse Source
This commit is contained in:
Chris Dumas
2026-05-25 13:16:57 +00:00
parent ea7ae9087e
commit 7b9ae307a5
6 changed files with 73 additions and 547 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
VIKUNJA.md
View File

@@ -46,6 +46,7 @@ This board is normalized to the shared playbook lane model.
- Feature work now lives on this board and should be tracked as separate tickets.
- Use the playbook lane names exactly when routing work.
- When a ticket finishes `In Dev`, Neo merges the feature branch back to `develop`, leaves a merge-complete comment, and hands the ticket forward for validation rather than marking it done.
- When Morpheus routes work, send Neo the handoff directly and leave the ticket comment as a concise record of the lane change and next action; do not rely on the bucket comment as the only delivery path.
- After the merge, move the ticket into `Ready for Test` and then `Deploying to Dev` while the dev build/deploy proves the change.
- Trinity handles validation once the dev environment is ready, and the ticket only moves forward after the live check passes.
- QA promotion is a separate step after dev validation, not part of the merge itself.