From 030fa04d3436723707dbe234c08439a1512fd0d6 Mon Sep 17 00:00:00 2001 From: dave Date: Sat, 4 Apr 2026 11:11:02 +0000 Subject: [PATCH] huskies: done 468_story_exclude_git_worktrees_from_loc_command_output --- ...ns_and_timezone_in_default_project_toml.md | 28 ------------------- ...e_git_worktrees_from_loc_command_output.md | 19 +++++++++++++ 2 files changed, 19 insertions(+), 28 deletions(-) delete mode 100644 .huskies/work/1_backlog/469_bug_scaffold_missing_rate_limit_notifications_and_timezone_in_default_project_toml.md create mode 100644 .huskies/work/5_done/468_story_exclude_git_worktrees_from_loc_command_output.md diff --git a/.huskies/work/1_backlog/469_bug_scaffold_missing_rate_limit_notifications_and_timezone_in_default_project_toml.md b/.huskies/work/1_backlog/469_bug_scaffold_missing_rate_limit_notifications_and_timezone_in_default_project_toml.md deleted file mode 100644 index 88b7bca1..00000000 --- a/.huskies/work/1_backlog/469_bug_scaffold_missing_rate_limit_notifications_and_timezone_in_default_project_toml.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -name: "Scaffold missing rate_limit_notifications and timezone in default project.toml" ---- - -# Bug 469: Scaffold missing rate_limit_notifications and timezone in default project.toml - -## Description - -The scaffold template for `project.toml` does not include the `rate_limit_notifications` or `timezone` fields. New projects get defaults (notifications on, no timezone), but these settings aren't visible or documented in the generated config file. Users have to discover them manually. - -The 455 rename also stripped these fields from the huskies project's own `project.toml` because it was regenerated from the scaffold. - -## How to Reproduce - -1. Run `huskies init` on a new project -2. Check the generated `.huskies/project.toml` - -## Actual Result - -No `rate_limit_notifications` or `timezone` fields in generated project.toml. - -## Expected Result - -Both fields present with commented defaults so users know they exist. - -## Acceptance Criteria - -- [ ] Bug is fixed and verified diff --git a/.huskies/work/5_done/468_story_exclude_git_worktrees_from_loc_command_output.md b/.huskies/work/5_done/468_story_exclude_git_worktrees_from_loc_command_output.md new file mode 100644 index 00000000..b97dc560 --- /dev/null +++ b/.huskies/work/5_done/468_story_exclude_git_worktrees_from_loc_command_output.md @@ -0,0 +1,19 @@ +--- +name: "Exclude git worktrees from loc command output" +--- + +# Story 468: Exclude git worktrees from loc command output + +## User Story + +As a user running the `loc` bot command, I want worktree directories (`.huskies/worktrees/`) to be excluded from the file listing so that the output only shows project source files, not duplicated code from agent worktrees. + +## Acceptance Criteria + +- [ ] loc command excludes files under .huskies/worktrees/ from line counts +- [ ] loc command excludes files under target/ directories from line counts +- [ ] Unit test verifies worktree paths are filtered out + +## Out of Scope + +- TBD