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

Document post-dev handoff flow
Some checks failed
Playwright Holiday Property Booking / playwright (push) Has been cancelled
Details
Test & Build Holiday Property Booking / test-build (push) Has been cancelled
Details
Deploy Holiday Property Booking / deploy (push) Has been cancelled
Details

Browse Source
This commit is contained in:
Chris Dumas
2026-05-22 10:53:13 +00:00
parent 93e4279577
commit bf51d51a7b
3 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
VIKUNJA.md
View File

@@ -45,3 +45,7 @@ This board is normalized to the shared playbook lane model.
- Phase 1 foundation work lands first.
- 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.
- 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.