-
Notifications
You must be signed in to change notification settings - Fork 2
Preflight worktree branch PR i exact-head delivery #163
Copy link
Copy link
Open
Labels
deliveryAuto-created label for deliveryAuto-created label for deliveryexact-headAuto-created label for exact-headAuto-created label for exact-headmanagedAuto-created label for managedAuto-created label for managedplan-2026-09-15Auto-created label for plan-2026-09-15Auto-created label for plan-2026-09-15planfileAuto-created label for planfileAuto-created label for planfilepriority-highAuto-created label for priority-highAuto-created label for priority-highpriority: highworktreeAuto-created label for worktreeAuto-created label for worktree
Description
Activity
Metadata
Metadata
Assignees
Labels
deliveryAuto-created label for deliveryAuto-created label for deliveryexact-headAuto-created label for exact-headAuto-created label for exact-headmanagedAuto-created label for managedAuto-created label for managedplan-2026-09-15Auto-created label for plan-2026-09-15Auto-created label for plan-2026-09-15planfileAuto-created label for planfileAuto-created label for planfilepriority-highAuto-created label for priority-highAuto-created label for priority-highpriority: highworktreeAuto-created label for worktreeAuto-created label for worktree
Źródło: semcod/fixos project/ticket-024/optimization-plan.md, P7. Cel: przed implementacją wykrywać istniejący ticket, worktree, branch, PR, dirty state i remote HEAD; konflikt zatrzymuje proces z diagnozą. Delivery ma emitować dowód commit, PR, current HEAD, active ticket, actor i validator. Akceptacja: testy idempotencji, konfliktu i cleanup po merge, bez kasowania nieznanych danych.