fix: use cwd for ticket backend
This commit is contained in:
parent
9dc78d38bf
commit
3c36d1feb8
|
|
@ -555,9 +555,12 @@ where
|
||||||
crate::feature::builtin::ticket::TicketFeatureAccess::Lifecycle
|
crate::feature::builtin::ticket::TicketFeatureAccess::Lifecycle
|
||||||
}
|
}
|
||||||
};
|
};
|
||||||
|
// Ticket tools are typed operations over the currently checked-out work
|
||||||
|
// tree. Use the Pod cwd rather than the runtime workspace root so a
|
||||||
|
// dedicated Orchestrator worktree gets its own `.yoi/tickets` backend.
|
||||||
feature_registry.add_module(
|
feature_registry.add_module(
|
||||||
crate::feature::builtin::ticket::ticket_tools_feature_with_options(
|
crate::feature::builtin::ticket::ticket_tools_feature_with_options(
|
||||||
&workspace_root,
|
&cwd,
|
||||||
feature_config.ticket.enabled.then_some(ticket_access),
|
feature_config.ticket.enabled.then_some(ticket_access),
|
||||||
feature_config.ticket_orchestration.enabled,
|
feature_config.ticket_orchestration.enabled,
|
||||||
),
|
),
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue
Block a user