@dezkareid/osddt 1.11.6 → 1.11.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/index.js +21 -1
- package/package.json +1 -1
package/dist/index.js
CHANGED
|
@@ -126,7 +126,27 @@ const COMMAND_DEFINITIONS = [
|
|
|
126
126
|
{
|
|
127
127
|
name: 'osddt.continue',
|
|
128
128
|
description: 'Detect the current workflow phase and prompt the next command to run',
|
|
129
|
-
body: ({ args, npxCommand }) => `${getRepoPreamble(npxCommand)}
|
|
129
|
+
body: ({ args, npxCommand }) => `${getRepoPreamble(npxCommand)}### Resolving the Feature Name and Working Directory
|
|
130
|
+
|
|
131
|
+
Use the following logic to determine the working directory:
|
|
132
|
+
|
|
133
|
+
**If \`worktree-repository\` is present in \`.osddtrc\` (worktree mode):**
|
|
134
|
+
|
|
135
|
+
1. If arguments were provided, derive the feature name from them:
|
|
136
|
+
- If the argument looks like a branch name (no spaces, kebab-case or slash-separated), use the last segment (after the last \`/\`, or the full value if no \`/\` is present).
|
|
137
|
+
- Otherwise convert it to a feature name following the Feature Name Constraints.
|
|
138
|
+
2. Run \`${npxCommand} worktree-info\` (pass \`<feature-name>\` as argument if one was derived, otherwise run without arguments):
|
|
139
|
+
- exit code **0**: parse the JSON and use the returned \`workingDir\` as the working directory.
|
|
140
|
+
- exit code **1**: no matching worktree found — fall back to the standard resolution below.
|
|
141
|
+
|
|
142
|
+
**If \`worktree-repository\` is absent in \`.osddtrc\` (standard mode), or after a worktree-info fallback:**
|
|
143
|
+
|
|
144
|
+
1. If arguments were provided, derive the feature name (same rules as above).
|
|
145
|
+
2. If **no arguments were provided**:
|
|
146
|
+
- List all folders under \`<project-path>/working-on/\`.
|
|
147
|
+
- If there is **only one folder**, use it automatically and inform the user.
|
|
148
|
+
- If there are **multiple folders**, present the list to the user and ask them to pick one.
|
|
149
|
+
- If there are **no folders**, inform the user that no in-progress features were found and stop.
|
|
130
150
|
|
|
131
151
|
## Instructions
|
|
132
152
|
|