tasktree 0.0.18__tar.gz → 0.0.19__tar.gz

tasktree-0.0.19/.github/ISSUE_TEMPLATES/bug_report.yml

@@ -0,0 +1,75 @@
+name: Bug report
+description: Create a report to help us improve
+title: "[BUG] <describe bug>"
+labels: [bug]
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        **Please fill out as much of this form as possible. Incomplete reports may slow triage.**
+
+  - type: input
+    id: summary
+    attributes:
+      label: Bug Summary
+      description: Short summary of the bug (1-2 sentences).
+      placeholder: "Unexpected crash when saving file"
+
+  - type: textarea
+    id: steps
+    attributes:
+      label: Steps to Reproduce
+      description: Step-by-step description to reproduce the bug.
+      placeholder: |
+        1. Open the application
+        2. Click on "Save"
+        3. Observe the error
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Behavior
+      description: What did you expect to happen?
+      placeholder: App should save the file without errors.
+
+  - type: textarea
+    id: actual
+    attributes:
+      label: Actual Behavior
+      description: What actually happens?
+      placeholder: "Error dialog appears: 'Failed to save'."
+
+  - type: dropdown
+    id: system
+    attributes:
+      label: Environment
+      multiple: true
+      options:
+        - Linux (Debian-based)
+        - Linux (other)
+        - Windows
+        - macOS
+        - Other (please describe below)
+      description: Select all platforms where this bug occurs.
+
+  - type: input
+    id: version
+    attributes:
+      label: Version(s)
+      description: App and/or OS version numbers (paste output, e.g. `git describe`, `uname -a`, etc.)
+      placeholder: "v1.2.3, Debian 12.4, kernel 6.1.0..."
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant Logs/Backtrace
+      description: Paste relevant logs, stack traces, or error messages. Use triple backticks for code.
+      render: shell
+
+  - type: textarea
+    id: extra
+    attributes:
+      label: Additional Context
+      description: Anything else useful for diagnosis? (Configurations, screenshots, external resources, etc.)
+      placeholder: "N/A"

tasktree-0.0.19/.github/ISSUE_TEMPLATES/feature_request.yml

@@ -0,0 +1,59 @@
+name: Feature request
+description: Suggest a new feature or improvement for this project
+title: "[Feature] <concise feature title>"
+labels: [enhancement]
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        **Thanks for suggesting an improvement! Please provide as much context as possible.**
+
+  - type: input
+    id: summary
+    attributes:
+      label: Feature Summary
+      description: Short, high-level summary of the requested feature.
+      placeholder: "Add support for IPv6 packet inspection"
+
+  - type: textarea
+    id: motivation
+    attributes:
+      label: Motivation & Use Case
+      description: What problem does this solve? Who benefits? Why is this needed?
+      placeholder: |
+        Currently, only IPv4 is supported in the firewall module. Many environments use IPv6 and need equivalent inspection features.
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Feature Description & Requirements
+      description: Describe the change or new capability. List any requirements or constraints.
+      placeholder: |
+        - Support parsing and filtering of IPv6 packets in filter mode.
+        - Update UI to allow IPv6 rule specification.
+        - Follow current module design patterns.
+
+  - type: textarea
+    id: impact
+    attributes:
+      label: Impact/Alternatives
+      description: How does this improve the project? Are there workarounds or competing solutions?
+      placeholder: |
+        Improves feature parity with other products; current workaround requires separate external processing.
+
+  - type: textarea
+    id: implementation
+    attributes:
+      label: Implementation notes (optional)
+      description: If you have ideas about implementing this, list them here (API ideas, design notes, related RFCs, etc.)
+      placeholder: |
+        - May require libc updates (for older distros)
+        - Reference: RFC 8200
+
+  - type: textarea
+    id: extra
+    attributes:
+      label: Additional context
+      description: Add any other context, mockups, references, or screenshots here.
+      placeholder: "N/A"

{tasktree-0.0.18 → tasktree-0.0.19}/.github/workflows/claude-code-review.yml

@@ -48,6 +48,8 @@ jobs:
             - Test coverage
 
             Use the repository's CLAUDE.md for guidance on style and conventions. Be constructive and helpful in your feedback.
+            
+            At the end of the review, create a tickbox list of the actions arising from the review, suitable for pasting into a comment for Claude Code to work on.
 
             Use `gh pr comment` with your Bash tool to leave your review as a comment on the PR.
 

{tasktree-0.0.18 → tasktree-0.0.19}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: tasktree
-Version: 0.0.18
+Version: 0.0.19
 Summary: A task automation tool with incremental execution
 Requires-Python: >=3.11
 Requires-Dist: click>=8.1.0
@@ -248,6 +248,7 @@ tasks:
     outputs: [dist/binary]                 # Output files (glob patterns)
     working_dir: subproject/               # Execution directory (default: project root)
     env: bash-strict                       # Execution environment (optional)
+    private: false                         # Hide from --list output (default: false)
     args:                                   # Task parameters
       - param1                              # Simple argument
       - param2: { type: path, default: "." }  # With type and default
@@ -687,6 +688,185 @@ tasks:
     cmd: echo "All tests passed"
 ```
 
+### Dependency Output References
+
+Tasks can reference named outputs from their dependencies, enabling dynamic workflows where build artifacts, generated filenames, and other values are passed between tasks.
+
+**Named Outputs:**
+
+Tasks can define outputs with names for easy referencing:
+
+```yaml
+tasks:
+  build:
+    outputs:
+      - bundle: "dist/app.js"        # Named output
+      - sourcemap: "dist/app.js.map" # Named output
+    cmd: webpack build
+
+  deploy:
+    deps: [build]
+    cmd: |
+      echo "Deploying {{ dep.build.outputs.bundle }}"
+      scp {{ dep.build.outputs.bundle }} server:/var/www/
+      scp {{ dep.build.outputs.sourcemap }} server:/var/www/
+```
+
+**Syntax:**
+
+- **Defining named outputs**: `outputs: [{ name: "path/to/file" }]`
+- **Referencing outputs**: `{{ dep.task_name.outputs.output_name }}`
+- **Mixed format**: Can combine named and anonymous outputs in the same task
+
+**Examples:**
+
+```yaml
+tasks:
+  # Generate a config file
+  generate-config:
+    outputs:
+      - config: "build/config.json"
+    cmd: |
+      mkdir -p build
+      echo '{"version": "1.0.0"}' > build/config.json
+
+  # Compile using the generated config
+  compile:
+    deps: [generate-config]
+    outputs:
+      - binary: "build/app"
+      - symbols: "build/app.sym"
+    cmd: |
+      echo "Using config: {{ dep.generate-config.outputs.config }}"
+      gcc -o build/app src/*.c
+
+  # Package multiple dependency outputs
+  package:
+    deps: [compile]
+    outputs:
+      - archive: "dist/app.tar.gz"
+    cmd: |
+      mkdir -p dist
+      tar czf {{ dep.package.outputs.archive }} \
+        {{ dep.compile.outputs.binary }} \
+        {{ dep.compile.outputs.symbols }}
+```
+
+**Mixed Named and Anonymous Outputs:**
+
+Tasks can have both named and anonymous outputs:
+
+```yaml
+tasks:
+  build:
+    outputs:
+      - binary: "build/app"      # Named - can be referenced
+      - "build/app.debug"        # Anonymous - tracked but not referenceable
+      - manifest: "build/manifest.json"  # Named - can be referenced
+    cmd: make all
+```
+
+**Transitive References:**
+
+Output references work across multiple levels of dependencies:
+
+```yaml
+tasks:
+  base:
+    outputs:
+      - lib: "out/libbase.a"
+    cmd: gcc -c base.c -o out/libbase.a
+
+  middleware:
+    deps: [base]
+    outputs:
+      - lib: "out/libmiddleware.a"
+    cmd: |
+      # Reference the base library
+      gcc -c middleware.c {{ dep.base.outputs.lib }} -o out/libmiddleware.a
+
+  app:
+    deps: [middleware]
+    cmd: |
+      # Reference middleware, which transitively used base
+      gcc main.c {{ dep.middleware.outputs.lib }} -o app
+```
+
+**Key Behaviors:**
+
+- **Template resolution**: Output references are resolved during dependency graph planning (in topological order)
+- **Fail-fast validation**: Errors are caught before execution begins
+- **Clear error messages**: If an output name doesn't exist, you get a list of available named outputs
+- **Backward compatible**: Existing anonymous outputs (`outputs: ["file.txt"]`) work unchanged
+- **Automatic input tracking**: Named outputs are automatically tracked as implicit inputs for dependent tasks
+
+**Error Messages:**
+
+If you reference a non-existent output:
+
+```yaml
+tasks:
+  build:
+    outputs:
+      - bundle: "dist/app.js"
+    cmd: webpack build
+
+  deploy:
+    deps: [build]
+    cmd: echo "{{ dep.build.outputs.missing }}"  # Error!
+```
+
+You'll get a clear error before execution:
+
+```
+Task 'deploy' references output 'missing' from task 'build',
+but 'build' has no output named 'missing'.
+Available named outputs in 'build': bundle
+Hint: Define named outputs like: outputs: [{ missing: 'path/to/file' }]
+```
+
+**Use Cases:**
+
+- **Dynamic artifact names**: Pass generated filenames between tasks
+- **Build metadata**: Reference manifests, checksums, or version files
+- **Multi-stage builds**: Chain compilation steps with specific output references
+- **Deployment pipelines**: Reference exact artifacts to deploy
+- **Configuration propagation**: Pass generated config files through build stages
+
+
+### Private Tasks
+
+Sometimes you may want to define helper tasks that are useful as dependencies but shouldn't be listed when users run `tt --list`. Mark these tasks as private:
+
+```yaml
+tasks:
+  # Private helper task - hidden from --list
+  setup-deps:
+    private: true
+    cmd: |
+      npm install
+      pip install -r requirements.txt
+
+  # Public task that uses the helper
+  build:
+    deps: [setup-deps]
+    cmd: npm run build
+```
+
+**Behavior:**
+- `tt --list` shows only public tasks (`build` in this example)
+- Private tasks can still be executed: `tt setup-deps` works
+- Private tasks work normally as dependencies
+- By default, all tasks are public (`private: false`)
+
+**Use cases:**
+- Internal helper tasks that shouldn't be run directly
+- Implementation details you want to hide from users
+- Shared setup tasks across multiple public tasks
+
+Note that private tasks remain fully functional - they're only hidden from the list view. Users who know the task name can still execute it directly.
+
+
 ## Environment Variables
 
 Task Tree supports reading environment variables in two ways:
@@ -1028,6 +1208,42 @@ At the start of each invocation, state is checked for invalid task hashes and no
 
 Task Tree provides several command-line options for controlling task execution:
 
+### Recipe File Selection
+
+Task Tree automatically discovers recipe files in the current directory and parent directories. You can also explicitly specify which file to use.
+
+**Automatic Discovery:**
+
+Task Tree searches for recipe files in the following order of preference:
+
+1. **Standard recipe files** (searched first, in order):
+   - `tasktree.yaml`
+   - `tasktree.yml`
+   - `tt.yaml`
+
+2. **Import files** (searched only if no standard files found):
+   - `*.tasks` files (e.g., `build.tasks`, `deploy.tasks`)
+
+If multiple files of the same priority level exist in the same directory, Task Tree will report an error and ask you to specify which file to use with `--tasks`.
+
+**Manual Selection:**
+
+```bash
+# Specify a recipe file explicitly
+tt --tasks build.tasks build
+tt -T custom-recipe.yaml test
+
+# Useful when you have multiple recipe files in the same directory
+tt --tasks ci.yaml deploy
+```
+
+**File Search Behavior:**
+
+- Task Tree searches **upward** from the current directory to find recipe files
+- **Standard recipe files** (`.yaml`/`.yml`) are always preferred over `*.tasks` files
+- `*.tasks` files are typically used for imports and are only used as main recipes if no standard files exist
+- The `.tasktree-state` file is created in the directory containing the recipe file
+
 ### Execution Control
 
 ```bash

{tasktree-0.0.18 → tasktree-0.0.19}/README.md

@@ -233,6 +233,7 @@ tasks:
     outputs: [dist/binary]                 # Output files (glob patterns)
     working_dir: subproject/               # Execution directory (default: project root)
     env: bash-strict                       # Execution environment (optional)
+    private: false                         # Hide from --list output (default: false)
     args:                                   # Task parameters
       - param1                              # Simple argument
       - param2: { type: path, default: "." }  # With type and default
@@ -672,6 +673,185 @@ tasks:
     cmd: echo "All tests passed"
 ```
 
+### Dependency Output References
+
+Tasks can reference named outputs from their dependencies, enabling dynamic workflows where build artifacts, generated filenames, and other values are passed between tasks.
+
+**Named Outputs:**
+
+Tasks can define outputs with names for easy referencing:
+
+```yaml
+tasks:
+  build:
+    outputs:
+      - bundle: "dist/app.js"        # Named output
+      - sourcemap: "dist/app.js.map" # Named output
+    cmd: webpack build
+
+  deploy:
+    deps: [build]
+    cmd: |
+      echo "Deploying {{ dep.build.outputs.bundle }}"
+      scp {{ dep.build.outputs.bundle }} server:/var/www/
+      scp {{ dep.build.outputs.sourcemap }} server:/var/www/
+```
+
+**Syntax:**
+
+- **Defining named outputs**: `outputs: [{ name: "path/to/file" }]`
+- **Referencing outputs**: `{{ dep.task_name.outputs.output_name }}`
+- **Mixed format**: Can combine named and anonymous outputs in the same task
+
+**Examples:**
+
+```yaml
+tasks:
+  # Generate a config file
+  generate-config:
+    outputs:
+      - config: "build/config.json"
+    cmd: |
+      mkdir -p build
+      echo '{"version": "1.0.0"}' > build/config.json
+
+  # Compile using the generated config
+  compile:
+    deps: [generate-config]
+    outputs:
+      - binary: "build/app"
+      - symbols: "build/app.sym"
+    cmd: |
+      echo "Using config: {{ dep.generate-config.outputs.config }}"
+      gcc -o build/app src/*.c
+
+  # Package multiple dependency outputs
+  package:
+    deps: [compile]
+    outputs:
+      - archive: "dist/app.tar.gz"
+    cmd: |
+      mkdir -p dist
+      tar czf {{ dep.package.outputs.archive }} \
+        {{ dep.compile.outputs.binary }} \
+        {{ dep.compile.outputs.symbols }}
+```
+
+**Mixed Named and Anonymous Outputs:**
+
+Tasks can have both named and anonymous outputs:
+
+```yaml
+tasks:
+  build:
+    outputs:
+      - binary: "build/app"      # Named - can be referenced
+      - "build/app.debug"        # Anonymous - tracked but not referenceable
+      - manifest: "build/manifest.json"  # Named - can be referenced
+    cmd: make all
+```
+
+**Transitive References:**
+
+Output references work across multiple levels of dependencies:
+
+```yaml
+tasks:
+  base:
+    outputs:
+      - lib: "out/libbase.a"
+    cmd: gcc -c base.c -o out/libbase.a
+
+  middleware:
+    deps: [base]
+    outputs:
+      - lib: "out/libmiddleware.a"
+    cmd: |
+      # Reference the base library
+      gcc -c middleware.c {{ dep.base.outputs.lib }} -o out/libmiddleware.a
+
+  app:
+    deps: [middleware]
+    cmd: |
+      # Reference middleware, which transitively used base
+      gcc main.c {{ dep.middleware.outputs.lib }} -o app
+```
+
+**Key Behaviors:**
+
+- **Template resolution**: Output references are resolved during dependency graph planning (in topological order)
+- **Fail-fast validation**: Errors are caught before execution begins
+- **Clear error messages**: If an output name doesn't exist, you get a list of available named outputs
+- **Backward compatible**: Existing anonymous outputs (`outputs: ["file.txt"]`) work unchanged
+- **Automatic input tracking**: Named outputs are automatically tracked as implicit inputs for dependent tasks
+
+**Error Messages:**
+
+If you reference a non-existent output:
+
+```yaml
+tasks:
+  build:
+    outputs:
+      - bundle: "dist/app.js"
+    cmd: webpack build
+
+  deploy:
+    deps: [build]
+    cmd: echo "{{ dep.build.outputs.missing }}"  # Error!
+```
+
+You'll get a clear error before execution:
+
+```
+Task 'deploy' references output 'missing' from task 'build',
+but 'build' has no output named 'missing'.
+Available named outputs in 'build': bundle
+Hint: Define named outputs like: outputs: [{ missing: 'path/to/file' }]
+```
+
+**Use Cases:**
+
+- **Dynamic artifact names**: Pass generated filenames between tasks
+- **Build metadata**: Reference manifests, checksums, or version files
+- **Multi-stage builds**: Chain compilation steps with specific output references
+- **Deployment pipelines**: Reference exact artifacts to deploy
+- **Configuration propagation**: Pass generated config files through build stages
+
+
+### Private Tasks
+
+Sometimes you may want to define helper tasks that are useful as dependencies but shouldn't be listed when users run `tt --list`. Mark these tasks as private:
+
+```yaml
+tasks:
+  # Private helper task - hidden from --list
+  setup-deps:
+    private: true
+    cmd: |
+      npm install
+      pip install -r requirements.txt
+
+  # Public task that uses the helper
+  build:
+    deps: [setup-deps]
+    cmd: npm run build
+```
+
+**Behavior:**
+- `tt --list` shows only public tasks (`build` in this example)
+- Private tasks can still be executed: `tt setup-deps` works
+- Private tasks work normally as dependencies
+- By default, all tasks are public (`private: false`)
+
+**Use cases:**
+- Internal helper tasks that shouldn't be run directly
+- Implementation details you want to hide from users
+- Shared setup tasks across multiple public tasks
+
+Note that private tasks remain fully functional - they're only hidden from the list view. Users who know the task name can still execute it directly.
+
+
 ## Environment Variables
 
 Task Tree supports reading environment variables in two ways:
@@ -1013,6 +1193,42 @@ At the start of each invocation, state is checked for invalid task hashes and no
 
 Task Tree provides several command-line options for controlling task execution:
 
+### Recipe File Selection
+
+Task Tree automatically discovers recipe files in the current directory and parent directories. You can also explicitly specify which file to use.
+
+**Automatic Discovery:**
+
+Task Tree searches for recipe files in the following order of preference:
+
+1. **Standard recipe files** (searched first, in order):
+   - `tasktree.yaml`
+   - `tasktree.yml`
+   - `tt.yaml`
+
+2. **Import files** (searched only if no standard files found):
+   - `*.tasks` files (e.g., `build.tasks`, `deploy.tasks`)
+
+If multiple files of the same priority level exist in the same directory, Task Tree will report an error and ask you to specify which file to use with `--tasks`.
+
+**Manual Selection:**
+
+```bash
+# Specify a recipe file explicitly
+tt --tasks build.tasks build
+tt -T custom-recipe.yaml test
+
+# Useful when you have multiple recipe files in the same directory
+tt --tasks ci.yaml deploy
+```
+
+**File Search Behavior:**
+
+- Task Tree searches **upward** from the current directory to find recipe files
+- **Standard recipe files** (`.yaml`/`.yml`) are always preferred over `*.tasks` files
+- `*.tasks` files are typically used for imports and are only used as main recipes if no standard files exist
+- The `.tasktree-state` file is created in the directory containing the recipe file
+
 ### Execution Control
 
 ```bash

{tasktree-0.0.18 → tasktree-0.0.19}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "tasktree"
-version = "0.0.18"
+version = "0.0.19"
 description = "A task automation tool with incremental execution"
 readme = "README.md"
 requires-python = ">=3.11"

{tasktree-0.0.18 → tasktree-0.0.19}/schema/README.md

@@ -44,7 +44,7 @@ tasks:
    - **Name**: Task Tree
    - **Schema file**: Point to `schema/tasktree-schema.json`
    - **Schema version**: JSON Schema version 7
-   - **File path pattern**: `tasktree.yaml` or `tt.yaml`
+   - **File path pattern**: `*.tasks`, `tasktree.yaml`, `tt.yaml`, `tasktree.yml` or `tt.yml`
 
 ### Command Line Validation
 
@@ -86,7 +86,9 @@ tasks:
     desc: Build the application
     deps: [base.setup]
     inputs: ["src/**/*.rs"]
-    outputs: [target/release/bin]
+    outputs:
+      - binary: target/release/bin    # Named output - can be referenced
+      - target/release/bin.map        # Anonymous output
     cmd: cargo build --release
 
   test:
@@ -100,6 +102,8 @@ tasks:
     args: [environment, region=us-west-1]
     cmd: |
       echo "Deploying to {{ arg.environment }} in {{ arg.region }}"
+      # Reference named output from dependency
+      scp {{ dep.build.outputs.binary }} server:/opt/
       ./deploy.sh {{ arg.environment }} {{ arg.region }}
 ```