fix(executor): add untracked files check after task commits (#1074)
After committing task changes, the executor now checks for untracked files (git status --short | grep '^??') and handles them: commit if intentional, add to .gitignore if generated/runtime output. This prevents generated artifacts (build outputs, .env files, cache files) from being silently left untracked in the working tree. Changes: - execute-plan.md: Add step 6 to task commit protocol - gsd-executor.md: Add step 6 to task commit protocol Fixes #957
This commit is contained in:
@@ -337,6 +337,8 @@ git commit -m "{type}({phase}-{plan}): {concise task description}
|
||||
```
|
||||
|
||||
**5. Record hash:** `TASK_COMMIT=$(git rev-parse --short HEAD)` — track for SUMMARY.
|
||||
|
||||
**6. Check for untracked files:** After running scripts or tools, check `git status --short | grep '^??'`. For any new untracked files: commit if intentional, add to `.gitignore` if generated/runtime output. Never leave generated files untracked.
|
||||
</task_commit_protocol>
|
||||
|
||||
<summary_creation>
|
||||
|
||||
@@ -279,6 +279,15 @@ TASK_COMMIT=$(git rev-parse --short HEAD)
|
||||
TASK_COMMITS+=("Task ${TASK_NUM}: ${TASK_COMMIT}")
|
||||
```
|
||||
|
||||
**6. Check for untracked generated files:**
|
||||
```bash
|
||||
git status --short | grep '^??'
|
||||
```
|
||||
If new untracked files appeared after running scripts or tools, decide for each:
|
||||
- **Commit it** — if it's a source file, config, or intentional artifact
|
||||
- **Add to .gitignore** — if it's a generated/runtime output (build artifacts, `.env` files, cache files, compiled output)
|
||||
- Do NOT leave generated files untracked
|
||||
|
||||
</task_commit>
|
||||
|
||||
<step name="checkpoint_protocol">
|
||||
|
||||
Reference in New Issue
Block a user