/project

/project finds the local Git repository for a destination name (list) and an exact item ID. Invoke it as /project or $project with both values, or let the Kestra work flow call it after /next returns an item. It reads the item only when several repositories match the destination. Configured project paths take priority when available; each selected search tier is completed so competing matches can be resolved independently of discovery order.

How /project finds a repository

01 · InputRequire destination and itemUse the supplied list and exact item ID without inferring either value.

↓

02 · SearchFind Git repositoriesInspect configured projects first, then directly neighboring repositories if needed. Complete each tier before selecting candidates.

↓

03 · Multiple matches onlyChoose from the itemRead the complete item to identify its primary repository; use stable tie breaks if it does not distinguish candidates.

↓

04 · ReturnReturn path or statusReturn one absolute repository path, or report that the search found none or could not finish.

What /project does

1	Require	Reject a missing or blank list or exact item ID before searching.
2	Search	Search configured project directories first, then repositories directly inside their parent directories. Prefer the longest full repository name contained in the normalized destination; use repository family prefixes only when no full name matches.
3	Choose	For several matches, use the complete item to identify the primary repository, then apply stable tie breaks.
4	Return	Return one absolute path, not found, or search incomplete. Invalid input or a failed search is an error.