Greptile Summary

This PR adds an opt-in task_config.includes_mode = \"extend\" setting that makes a config file's task_config.includes additive rather than replacing the inherited includes. The implementation uses a recursive replacement_task_include_specs_for_dir function to walk the config precedence chain and accumulate includes from all configs that opt into extend mode, falling back to default_task_includes() when no more parents exist. The refactor also extracts configs_for_filename_at_root (now reversing glob results so that lexicographically later conf.d files have higher precedence) and adds a new task_git_includes_for_dir helper so git-URL entries follow the same stacking semantics as local paths.

Confidence Score: 5/5

Safe to merge — the recursive extend logic is correct and terminates, all prior review concerns are addressed, and the implementation is well-tested.

No P0 or P1 findings. The recursion in replacement_task_include_specs_for_dir terminates because each call adds exactly one config to exclude_paths against a finite set. The serde representation matches the JSON schema. The glob-reversal change for conf.d precedence is validated by the new unit test. Both code paths (project configs via task_include_specs_for_dir and global configs via load_file_tasks) handle extend mode consistently. The previously flagged issues (all-or-nothing merging, undocumented additive alias) are resolved.

No files require special attention.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[task_includes_for_dir] --> B[task_include_specs_for_dir]
    B --> C[configs_at_root]
    B --> D[replacement_task_include_specs_for_dir]
    D --> E{selected_task_include_config}
    E -- "None (no config with includes)" --> F[default_task_include_specs_for_dir]
    E -- "cf with includes_mode=Replace" --> G[task_include_specs_for_config cf]
    E -- "cf with includes_mode=Extend" --> H[exclude cf, recurse]
    H --> D
    H --> I[prepend inherited specs]
    I --> J[append task_include_specs_for_config cf]
    K[load_tasks_in_dir] --> A
    K --> L[task_git_includes_for_dir]
    L --> B
    M[load_file_tasks - global only] --> N{includes + mode?}
    N -- "Some + Extend" --> O[default_task_includes + config includes]
    N -- "Some + Replace" --> P[config includes only]
    N -- "None" --> Q[default_task_includes]

_{Reviews (11): Last reviewed commit: "Merge branch 'main' into task-includes-m..." | Re-trigger Greptile}

I don't really see much value in this, sorry. If you're using this why wouldn't you just list the directories you know you have?

My idea was to provide a way to avoid repeating the same entries in mise.local.toml, so I don't need to always update mise.local.toml.
I made this PR because I saw similar requests, but I agree that it doesn't worth for adding some complexity.