tasktree 0.0.1__tar.gz → 0.0.3__tar.gz

{tasktree-0.0.1 → tasktree-0.0.3}/.github/workflows/test.yml

@@ -12,7 +12,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        os: [ubuntu-latest, macos-latest, windows-latest]
+        os: [ubuntu-latest, macos-latest]
         python-version: ['3.11', '3.12']
 
     steps:

{tasktree-0.0.1 → tasktree-0.0.3}/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: tasktree
-Version: 0.0.1
-Summary: A task automation tool with intelligent incremental execution
+Version: 0.0.3
+Summary: A task automation tool with incremental execution
 Requires-Python: >=3.11
 Requires-Dist: click>=8.1.0
 Requires-Dist: colorama>=0.4.6
@@ -14,9 +14,9 @@ Description-Content-Type: text/markdown
 
 # Task Tree (tt)
 
-[![Tests](https://github.com/kevinchannon/tasktree/actions/workflows/test.yml/badge.svg)](https://github.com/kevinchannon/tasktree/actions/workflows/test.yml)
+[![Tests](https://github.com/kevinchannon/task-tree/actions/workflows/test.yml/badge.svg)](https://github.com/kevinchannon/task-tree/actions/workflows/test.yml)
 
-A task automation tool that combines simple command execution with intelligent dependency tracking and incremental execution.
+A task automation tool that combines simple command execution with dependency tracking and incremental execution.
 
 ## Installation
 
@@ -31,13 +31,13 @@ pipx install tasktree
 For the latest unreleased version from GitHub:
 
 ```bash
-pipx install git+https://github.com/kevinchannon/tasktree.git
+pipx install git+https://github.com/kevinchannon/task-tree.git
 ```
 
 Or to install from a local clone:
 
 ```bash
-git clone https://github.com/kevinchannon/tasktree.git
+git clone https://github.com/kevinchannon/task-tree.git
 cd tasktree
 pipx install .
 ```
@@ -72,11 +72,12 @@ tt --list         # Show all available tasks
 
 Task Tree only runs tasks when necessary. A task executes if:
 
-- Its definition (command, outputs, working directory) has changed
+- Its definition (command, outputs, working directory, environment) has changed
 - Any input files have changed since the last run
 - Any dependencies have re-run
 - It has never been executed before
 - It has no inputs or outputs (always runs)
+- The execution environment has changed (CLI override or environment config change)
 
 ### Automatic Input Inheritance
 
@@ -105,17 +106,25 @@ All state lives in `.tasktree-state` at your project root. Stale entries are aut
 ```yaml
 task-name:
   desc: Human-readable description (optional)
-  deps: [other-task]              # Task dependencies
-  inputs: [src/**/*.go]            # Explicit input files (glob patterns)
-  outputs: [dist/binary]           # Output files (glob patterns)
-  working_dir: subproject/         # Execution directory (default: project root)
-  args: [param1, param2:path=default]   # Task parameters
-  cmd: go build -o dist/binary     # Command to execute
+  deps: [other-task]                     # Task dependencies
+  inputs: [src/**/*.go]                  # Explicit input files (glob patterns)
+  outputs: [dist/binary]                 # Output files (glob patterns)
+  working_dir: subproject/               # Execution directory (default: project root)
+  env: bash-strict                       # Execution environment (optional)
+  args: [param1, param2:path=default]    # Task parameters
+  cmd: go build -o dist/binary           # Command to execute
 ```
 
 ### Commands
 
-Multi-line commands using YAML literal blocks:
+**Single-line commands** are executed directly via the configured shell:
+
+```yaml
+build:
+  cmd: cargo build --release
+```
+
+**Multi-line commands** are written to temporary script files for proper execution:
 
 ```yaml
 deploy:
@@ -125,7 +134,9 @@ deploy:
     rsync -av dist/ server:/opt/app/
 ```
 
-Or folded blocks for long single-line commands:
+Multi-line commands preserve shell syntax (line continuations, heredocs, etc.) and support shebangs on Unix/macOS.
+
+Or use folded blocks for long single-line commands:
 
 ```yaml
 compile:
@@ -136,6 +147,58 @@ compile:
     -L lib -lm
 ```
 
+### Execution Environments
+
+Configure custom shell environments for task execution:
+
+```yaml
+environments:
+  default: bash-strict
+
+  bash-strict:
+    shell: bash
+    args: ['-c']              # For single-line: bash -c "command"
+    preamble: |               # For multi-line: prepended to script
+      set -euo pipefail
+
+  python:
+    shell: python
+    args: ['-c']
+
+  powershell:
+    shell: powershell
+    args: ['-ExecutionPolicy', 'Bypass', '-Command']
+    preamble: |
+      $ErrorActionPreference = 'Stop'
+
+tasks:
+  build:
+    # Uses 'default' environment (bash-strict)
+    cmd: cargo build --release
+
+  analyze:
+    env: python
+    cmd: |
+      import sys
+      print(f"Analyzing with Python {sys.version}")
+      # ... analysis code ...
+
+  windows-task:
+    env: powershell
+    cmd: |
+      Compress-Archive -Path dist/* -DestinationPath package.zip
+```
+
+**Environment resolution priority:**
+1. CLI override: `tt --env python build`
+2. Task's `env` field
+3. Recipe's `default` environment
+4. Platform default (bash on Unix, cmd on Windows)
+
+**Platform defaults** when no environments are configured:
+- **Unix/macOS**: bash with `-c` args
+- **Windows**: cmd with `/c` args
+
 ### Parameterised Tasks
 
 Tasks can accept arguments with optional defaults:
@@ -202,12 +265,19 @@ Input and output patterns support standard glob syntax:
 
 ### How State Works
 
-Each task is identified by a hash of its definition (command, outputs, working directory). State tracks:
+Each task is identified by a hash of its definition. The hash includes:
+
+- Command to execute
+- Output patterns
+- Working directory
+- Argument definitions
+- Execution environment
 
+State tracks:
 - When the task last ran
 - Timestamps of input files at that time
 
-Tasks are re-run when their definition changes or inputs are newer than the last run.
+Tasks are re-run when their definition changes, inputs are newer than the last run, or the environment changes.
 
 ### What's Not In The Hash
 
@@ -222,6 +292,72 @@ Changes to these don't invalidate cached state:
 
 At the start of each invocation, state is checked for invalid task hashes and non-existent ones are automatically removed. Delete a task from your recipe file and its state disappears the next time you run `tt <cmd>`
 
+## Command-Line Options
+
+Task Tree provides several command-line options for controlling task execution:
+
+### Execution Control
+
+```bash
+# Force re-run (ignore freshness checks)
+tt --force build
+tt -f build
+
+# Run only the specified task, skip dependencies (implies --force)
+tt --only deploy
+tt -o deploy
+
+# Override environment for all tasks
+tt --env python analyze
+tt -e powershell build
+```
+
+### Information Commands
+
+```bash
+# List all available tasks
+tt --list
+tt -l
+
+# Show detailed task definition
+tt --show build
+
+# Show dependency tree (without execution)
+tt --tree deploy
+
+# Show version
+tt --version
+tt -v
+
+# Create a blank recipe file
+tt --init
+```
+
+### State Management
+
+```bash
+# Remove state file (reset task cache)
+tt --clean
+tt --clean-state
+tt --reset
+```
+
+### Common Workflows
+
+```bash
+# Fresh build of everything
+tt --force build
+
+# Run a task without rebuilding dependencies
+tt --only test
+
+# Test with a different shell/environment
+tt --env python test
+
+# Force rebuild and deploy
+tt --force deploy production
+```
+
 ## Example: Full Build Pipeline
 
 ```yaml
@@ -297,7 +433,7 @@ State file uses JSON format for simplicity and standard library compatibility.
 
 ```bash
 # Clone repository
-git clone https://github.com/kevinchannon/tasktree.git
+git clone https://github.com/kevinchannon/task-tree.git
 cd tasktree
 
 # Install uv (if not already installed)
@@ -363,8 +499,8 @@ git push origin v1.0.0
    - Publish to PyPI
 
 4. Verify the release:
-   - GitHub: https://github.com/kevinchannon/tasktree/releases
-   - PyPI: https://pypi.org/project/tasktree/
+   - GitHub: https://github.com/kevinchannon/task-tree/releases
+   - PyPI: https://pypi.org/kevinchannon/tasktree/
    - Test: `pipx install --force tasktree`
 
 ### Version Numbering
@@ -372,16 +508,4 @@ git push origin v1.0.0
 Follow semantic versioning:
 - `v1.0.0` - Major release (breaking changes)
 - `v1.1.0` - Minor release (new features, backward compatible)
-- `v1.1.1` - Patch release (bug fixes)
-
-### PyPI Trusted Publishing Setup
-
-Before the first release, configure trusted publishing on PyPI:
-
-1. Go to https://pypi.org/manage/account/publishing/
-2. Add a new publisher:
-   - **PyPI Project Name**: `tasktree`
-   - **Owner**: `kevinchannon`
-   - **Repository name**: `tasktree`
-   - **Workflow name**: `release.yml`
-   - **Environment name**: (leave blank)
+- `v1.1.1` - Patch release (bug fixes)

{tasktree-0.0.1 → tasktree-0.0.3}/README.md

@@ -1,8 +1,8 @@
 # Task Tree (tt)
 
-[![Tests](https://github.com/kevinchannon/tasktree/actions/workflows/test.yml/badge.svg)](https://github.com/kevinchannon/tasktree/actions/workflows/test.yml)
+[![Tests](https://github.com/kevinchannon/task-tree/actions/workflows/test.yml/badge.svg)](https://github.com/kevinchannon/task-tree/actions/workflows/test.yml)
 
-A task automation tool that combines simple command execution with intelligent dependency tracking and incremental execution.
+A task automation tool that combines simple command execution with dependency tracking and incremental execution.
 
 ## Installation
 
@@ -17,13 +17,13 @@ pipx install tasktree
 For the latest unreleased version from GitHub:
 
 ```bash
-pipx install git+https://github.com/kevinchannon/tasktree.git
+pipx install git+https://github.com/kevinchannon/task-tree.git
 ```
 
 Or to install from a local clone:
 
 ```bash
-git clone https://github.com/kevinchannon/tasktree.git
+git clone https://github.com/kevinchannon/task-tree.git
 cd tasktree
 pipx install .
 ```
@@ -58,11 +58,12 @@ tt --list         # Show all available tasks
 
 Task Tree only runs tasks when necessary. A task executes if:
 
-- Its definition (command, outputs, working directory) has changed
+- Its definition (command, outputs, working directory, environment) has changed
 - Any input files have changed since the last run
 - Any dependencies have re-run
 - It has never been executed before
 - It has no inputs or outputs (always runs)
+- The execution environment has changed (CLI override or environment config change)
 
 ### Automatic Input Inheritance
 
@@ -91,17 +92,25 @@ All state lives in `.tasktree-state` at your project root. Stale entries are aut
 ```yaml
 task-name:
   desc: Human-readable description (optional)
-  deps: [other-task]              # Task dependencies
-  inputs: [src/**/*.go]            # Explicit input files (glob patterns)
-  outputs: [dist/binary]           # Output files (glob patterns)
-  working_dir: subproject/         # Execution directory (default: project root)
-  args: [param1, param2:path=default]   # Task parameters
-  cmd: go build -o dist/binary     # Command to execute
+  deps: [other-task]                     # Task dependencies
+  inputs: [src/**/*.go]                  # Explicit input files (glob patterns)
+  outputs: [dist/binary]                 # Output files (glob patterns)
+  working_dir: subproject/               # Execution directory (default: project root)
+  env: bash-strict                       # Execution environment (optional)
+  args: [param1, param2:path=default]    # Task parameters
+  cmd: go build -o dist/binary           # Command to execute
 ```
 
 ### Commands
 
-Multi-line commands using YAML literal blocks:
+**Single-line commands** are executed directly via the configured shell:
+
+```yaml
+build:
+  cmd: cargo build --release
+```
+
+**Multi-line commands** are written to temporary script files for proper execution:
 
 ```yaml
 deploy:
@@ -111,7 +120,9 @@ deploy:
     rsync -av dist/ server:/opt/app/
 ```
 
-Or folded blocks for long single-line commands:
+Multi-line commands preserve shell syntax (line continuations, heredocs, etc.) and support shebangs on Unix/macOS.
+
+Or use folded blocks for long single-line commands:
 
 ```yaml
 compile:
@@ -122,6 +133,58 @@ compile:
     -L lib -lm
 ```
 
+### Execution Environments
+
+Configure custom shell environments for task execution:
+
+```yaml
+environments:
+  default: bash-strict
+
+  bash-strict:
+    shell: bash
+    args: ['-c']              # For single-line: bash -c "command"
+    preamble: |               # For multi-line: prepended to script
+      set -euo pipefail
+
+  python:
+    shell: python
+    args: ['-c']
+
+  powershell:
+    shell: powershell
+    args: ['-ExecutionPolicy', 'Bypass', '-Command']
+    preamble: |
+      $ErrorActionPreference = 'Stop'
+
+tasks:
+  build:
+    # Uses 'default' environment (bash-strict)
+    cmd: cargo build --release
+
+  analyze:
+    env: python
+    cmd: |
+      import sys
+      print(f"Analyzing with Python {sys.version}")
+      # ... analysis code ...
+
+  windows-task:
+    env: powershell
+    cmd: |
+      Compress-Archive -Path dist/* -DestinationPath package.zip
+```
+
+**Environment resolution priority:**
+1. CLI override: `tt --env python build`
+2. Task's `env` field
+3. Recipe's `default` environment
+4. Platform default (bash on Unix, cmd on Windows)
+
+**Platform defaults** when no environments are configured:
+- **Unix/macOS**: bash with `-c` args
+- **Windows**: cmd with `/c` args
+
 ### Parameterised Tasks
 
 Tasks can accept arguments with optional defaults:
@@ -188,12 +251,19 @@ Input and output patterns support standard glob syntax:
 
 ### How State Works
 
-Each task is identified by a hash of its definition (command, outputs, working directory). State tracks:
+Each task is identified by a hash of its definition. The hash includes:
+
+- Command to execute
+- Output patterns
+- Working directory
+- Argument definitions
+- Execution environment
 
+State tracks:
 - When the task last ran
 - Timestamps of input files at that time
 
-Tasks are re-run when their definition changes or inputs are newer than the last run.
+Tasks are re-run when their definition changes, inputs are newer than the last run, or the environment changes.
 
 ### What's Not In The Hash
 
@@ -208,6 +278,72 @@ Changes to these don't invalidate cached state:
 
 At the start of each invocation, state is checked for invalid task hashes and non-existent ones are automatically removed. Delete a task from your recipe file and its state disappears the next time you run `tt <cmd>`
 
+## Command-Line Options
+
+Task Tree provides several command-line options for controlling task execution:
+
+### Execution Control
+
+```bash
+# Force re-run (ignore freshness checks)
+tt --force build
+tt -f build
+
+# Run only the specified task, skip dependencies (implies --force)
+tt --only deploy
+tt -o deploy
+
+# Override environment for all tasks
+tt --env python analyze
+tt -e powershell build
+```
+
+### Information Commands
+
+```bash
+# List all available tasks
+tt --list
+tt -l
+
+# Show detailed task definition
+tt --show build
+
+# Show dependency tree (without execution)
+tt --tree deploy
+
+# Show version
+tt --version
+tt -v
+
+# Create a blank recipe file
+tt --init
+```
+
+### State Management
+
+```bash
+# Remove state file (reset task cache)
+tt --clean
+tt --clean-state
+tt --reset
+```
+
+### Common Workflows
+
+```bash
+# Fresh build of everything
+tt --force build
+
+# Run a task without rebuilding dependencies
+tt --only test
+
+# Test with a different shell/environment
+tt --env python test
+
+# Force rebuild and deploy
+tt --force deploy production
+```
+
 ## Example: Full Build Pipeline
 
 ```yaml
@@ -283,7 +419,7 @@ State file uses JSON format for simplicity and standard library compatibility.
 
 ```bash
 # Clone repository
-git clone https://github.com/kevinchannon/tasktree.git
+git clone https://github.com/kevinchannon/task-tree.git
 cd tasktree
 
 # Install uv (if not already installed)
@@ -349,8 +485,8 @@ git push origin v1.0.0
    - Publish to PyPI
 
 4. Verify the release:
-   - GitHub: https://github.com/kevinchannon/tasktree/releases
-   - PyPI: https://pypi.org/project/tasktree/
+   - GitHub: https://github.com/kevinchannon/task-tree/releases
+   - PyPI: https://pypi.org/kevinchannon/tasktree/
    - Test: `pipx install --force tasktree`
 
 ### Version Numbering
@@ -358,16 +494,4 @@ git push origin v1.0.0
 Follow semantic versioning:
 - `v1.0.0` - Major release (breaking changes)
 - `v1.1.0` - Minor release (new features, backward compatible)
-- `v1.1.1` - Patch release (bug fixes)
-
-### PyPI Trusted Publishing Setup
-
-Before the first release, configure trusted publishing on PyPI:
-
-1. Go to https://pypi.org/manage/account/publishing/
-2. Add a new publisher:
-   - **PyPI Project Name**: `tasktree`
-   - **Owner**: `kevinchannon`
-   - **Repository name**: `tasktree`
-   - **Workflow name**: `release.yml`
-   - **Environment name**: (leave blank)
+- `v1.1.1` - Patch release (bug fixes)

{tasktree-0.0.1 → tasktree-0.0.3}/pyproject.toml

@@ -1,7 +1,7 @@
 [project]
 name = "tasktree"
-version = "0.0.1"
-description = "A task automation tool with intelligent incremental execution"
+version = "0.0.3"
+description = "A task automation tool with incremental execution"
 readme = "README.md"
 requires-python = ">=3.11"
 dependencies = [