dbt-autofix 0.0.0.post1.dev0__tar.gz

dbt_autofix-0.0.0.post1.dev0/.claude/skills/add-integration-test/SKILL.md

@@ -0,0 +1,176 @@
+---
+name: add-integration-test
+description: Create a new integration test for dbt-autofix with proper folder structure and golden files
+disable-model-invocation: true
+argument-hint: [project-name]
+allowed-tools: Read, Write, Bash, Glob, Grep, Edit
+---
+
+# Add Integration Test
+
+Create a new integration test for dbt-autofix. Integration tests verify that the refactor tool correctly transforms dbt projects.
+
+## Philosophy: Test-Driven Development
+
+**Integration tests document DESIRED behavior, not current behavior.**
+
+- For bug fixes: Create a test that reproduces the bug, with expected output showing the correct behavior
+- For feature requests: Create a test that specifies what the feature should do
+- Tests should FAIL initially, then PASS once the fix/feature is implemented
+
+This approach:
+1. Serves as a specification for the work
+2. Prevents regressions
+3. Automatically validates when the implementation is complete
+
+**Using GOLDIE_UPDATE:** Run with `GOLDIE_UPDATE=1` to understand *current* behavior, but don't blindly accept it as the expected output. Manually craft the `_expected` files to reflect what the behavior *should* be.
+
+## Arguments
+
+- `$ARGUMENTS` - The test project name (e.g., `config_quoted_strings`)
+
+**Running a single test:**
+```bash
+uv run pytest "tests/integration_tests/test_full_dbt_projects.py::test_project_refactor[project_<name>]" -v
+```
+
+Example for a project named `config_quoted_strings`:
+```bash
+uv run pytest "tests/integration_tests/test_full_dbt_projects.py::test_project_refactor[project_config_quoted_strings]" -v
+```
+
+**Naming guidance:** Use descriptive names that explain what the test covers, not issue numbers. For example:
+- `config_quoted_strings` (not `issue_221`)
+- `python_model_meta_config` (not `issue_220`)
+- `jinja_unmatched_endif`
+
+The name becomes `project_<name>` in the test projects directory.
+
+## Test Structure
+
+Each integration test requires 3 artifacts in `tests/integration_tests/dbt_projects/`:
+
+1. **`project_<name>/`** - Input dbt project (before refactor)
+   - Minimum: `dbt_project.yml` + model files in `models/`
+
+2. **`project_<name>_expected/`** - Expected output (after refactor)
+   - Mirror of input with the DESIRED transformations applied
+
+3. **`project_<name>_expected.stdout`** - Expected JSON log output
+   - One JSON object per line documenting refactors that SHOULD be applied
+
+## Steps to Follow
+
+### Step 1: Gather Information
+
+**Reference the README** for the authoritative list of deprecations: [README.md](../../../README.md)
+
+**Discover existing test projects** to see patterns and avoid duplication:
+```bash
+ls tests/integration_tests/dbt_projects/ | grep -v _expected
+```
+
+Ask the user:
+1. What deprecation, bug, or behavior is being tested?
+2. Is there a GitHub issue number to reference?
+3. Does this test need special flags?
+   - `--behavior-change` mode
+   - `--semantic-layer` mode
+
+### Step 2: Understand Current Behavior (Optional)
+
+Run with `GOLDIE_UPDATE=1` to see what the tool currently does:
+
+```bash
+GOLDIE_UPDATE=1 uv run pytest "tests/integration_tests/test_full_dbt_projects.py::test_project_refactor[project_<name>]" -v
+```
+
+**Note:** Do NOT commit the auto-generated `_expected` files from `GOLDIE_UPDATE` without review. They reflect current behavior, not necessarily desired behavior. Manually craft the expected output to reflect what the behavior *should* be.
+
+### Step 3: Create Project Structure
+
+```
+tests/integration_tests/dbt_projects/
+├── project_<name>/
+│   ├── dbt_project.yml
+│   └── models/
+│       └── <model>.sql (or .py for Python models)
+├── project_<name>_expected/
+│   ├── dbt_project.yml
+│   └── models/
+│       └── <model>.sql
+└── project_<name>_expected.stdout
+```
+
+**Minimal `dbt_project.yml`:**
+```yaml
+name: '<test name>'
+version: '1.0.0'
+config-version: 2
+
+profile: 'default'
+
+model-paths: ["models"]
+```
+
+### Step 4: Create Test Models (Input)
+
+Create model files that demonstrate the behavior being tested. The input should contain the pattern that triggers the deprecation/refactor.
+
+### Step 5: Create Expected Output (Desired Behavior)
+
+Manually create the `_expected` files showing what the output SHOULD be after the fix/feature is implemented. Do NOT just copy current behavior.
+
+### Step 6: Create Expected stdout
+
+Write the JSON log output that SHOULD be produced. Each line is a JSON object:
+
+```json
+{"mode": "applied", "file_path": "...", "refactors": [{"deprecation": "...", "log": "..."}]}
+{"mode": "complete"}
+```
+
+### Step 7: Handle Special Modes (if needed)
+
+If the test requires `--behavior-change` or `--semantic-layer`, add an entry to the dicts in `tests/integration_tests/test_full_dbt_projects.py`:
+
+```python
+project_dir_to_behavior_change_mode["project_<name>"] = True
+# or
+project_dir_to_semantic_layer_mode["project_<name>"] = True
+```
+
+### Step 8: Verify Test Behavior
+
+```bash
+# Should fail (or xfail) if feature not implemented
+uv run pytest "tests/integration_tests/test_full_dbt_projects.py::test_project_refactor[project_<name>]" -v
+
+# Should pass once feature is implemented
+```
+
+## Golden File Tips
+
+- `GOLDIE_UPDATE=1` shows current behavior - use for understanding, not as source of truth
+- The `file_path` key is ignored during comparison (paths don't need to match)
+- Blank lines are ignored in file comparisons
+- The `_expected` suffix must match exactly
+- Include trailing newlines in files
+
+## Example Workflows
+
+### Bug Fix (quoted strings causing errors)
+
+1. Create `project_config_quoted_strings/` with a model containing the problematic quoted string
+2. Create `project_config_quoted_strings_expected/` showing correct handling (no error, proper transformation)
+3. Test fails initially (bug exists)
+4. Fix the bug
+5. Test passes (bug fixed)
+
+### Feature Request (Python model custom config access)
+
+1. Create `project_python_model_meta_config/` with a Python model using `dbt.config.get("custom_key")`
+2. Create `project_python_model_meta_config_expected/` showing the Python code updated to `dbt.config.get("meta").get("custom_key")`
+3. Test fails initially (feature not implemented)
+4. Implement feature
+5. Test passes (feature complete)

dbt_autofix-0.0.0.post1.dev0/.github/CODEOWNERS

@@ -0,0 +1,6 @@
+* @chayac @dbt-labs/dbt-package-owners
+
+
+### Deprecations
+
+/src/dbt_autofix/deprecations.py    @dbt-labs/growth-pricing

dbt_autofix-0.0.0.post1.dev0/.github/dependabot.yml

@@ -0,0 +1,16 @@
+version: 2
+updates:
+  # Enable version updates for API
+  - package-ecosystem: "uv"
+    # Look for `pyproject.toml` and `uv.lock` file in the `root` directory
+    directory: "/"
+    schedule:
+      interval: "daily"
+
+  # Enable version updates for GitHub Actions
+  - package-ecosystem: "github-actions"
+    # Workflow files stored in the default location of `.github/workflows`
+    # You don't need to specify `/.github/workflows` for `directory`. You can use `directory: "/"`.
+    directory: "/"
+    schedule:
+      interval: "weekly"

dbt_autofix-0.0.0.post1.dev0/.github/pull_request_template.md

@@ -0,0 +1,22 @@
+## Description
+
+Please describe the changes made and why they were made. Link to any relevant issues or tickets.
+
+## Type of change
+
+*   [ ] Bug fix (non-breaking change which fixes an issue)
+*   [ ] New feature (non-breaking change which adds functionality)
+*   [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+*   [ ] Documentation update
+
+## Checklist
+
+*   [ ] Ran `uv run ruff check . --config pyproject.toml`
+*   [ ] Ran `uv run ruff format --config pyproject.toml`
+*   [ ] Ran `uv run ty check`
+*   [ ] If this is a bug fix:
+    *   [ ] Updated integration tests with bug repro
+    *   [ ] Linked to bug report ticket
+*   [ ] Added unit tests if needed
+*   [ ] Updated unit tests if needed
+*   [ ] Tests passed when run locally

dbt_autofix-0.0.0.post1.dev0/.github/workflows/nox-pr.yml

@@ -0,0 +1,15 @@
+name: Run Nox on PR
+
+on:
+  pull_request:
+    types: [opened, synchronize, reopened]
+
+jobs:
+  nox:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # actions/checkout@v4
+      - name: Install uv
+        uses: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86 # astral-sh/setup-uv@v5
+      - uses: fjwillemsen/setup-nox2@da319daa4a57af7b0802d65173dd08b7e902fa08 # fjwillemsen/setup-nox2@v4.0.0
+      - run: nox

dbt_autofix-0.0.0.post1.dev0/.github/workflows/pytest-pr.yml

@@ -0,0 +1,48 @@
+name: Run Pytest
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    types: [opened, synchronize, reopened]
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    name: test on ${{ matrix.python-version }}
+    runs-on: ubuntu-latest
+    continue-on-error: true
+    timeout-minutes: 5
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v7
+
+      - uses: astral-sh/setup-uv@e58605a9b6da7c637471fab8847a5e5a6b8df081 # v5
+        with:
+          python-version: ${{ matrix.python-version }}
+          enable-cache: true
+          cache-suffix: test
+
+      - run: uv sync --all-packages
+      - run: uv run pytest
+
+  static-analysis:
+    name: static analysis
+    runs-on: ubuntu-latest
+    timeout-minutes: 5
+    steps:
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@e58605a9b6da7c637471fab8847a5e5a6b8df081 # v5
+        with:
+          python-version: "3.10"
+          enable-cache: true
+          cache-suffix: static-analysis
+      - run: uv sync --all-packages
+      - run: uv run ruff check . --config pyproject.toml --output-format github
+      - run: uv run ruff format --check --diff . --config pyproject.toml
+      - run: uv run ty check --output-format github

dbt_autofix-0.0.0.post1.dev0/.github/workflows/release.yml

@@ -0,0 +1,52 @@
+name: Release
+
+on:
+  workflow_dispatch:
+    inputs:
+      deploy-to:
+        type: choice
+        description: Choose where to publish (test/prod)
+        options:
+          - PypiProd
+          - PypiTest
+        default: PypiTest
+  push:
+    tags:
+      - 'v*'
+
+permissions: read-all
+
+# will cancel previous workflows triggered by the same event and for the same ref for PRs or same SHA otherwise
+concurrency:
+  group: ${{ github.workflow }}-${{ github.event_name }}-${{ contains(github.event_name, 'pull_request') && github.event.pull_request.head.ref || github.sha }}
+  cancel-in-progress: true
+
+jobs:
+
+  release:
+    name: PyPI - ${{ inputs.deploy-to || 'PypiProd' }}
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write  # IMPORTANT: this permission is mandatory for trusted publishing
+
+    steps:
+      - name: Check out repository
+        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # actions/checkout@v4
+        with:
+          persist-credentials: false
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@caf0cab7a618c569241d31dcd442f54681755d39 # astral-sh/setup-uv@v3
+
+      - name: Build artifacts
+        run: uv build --all
+
+      - name: Publish artifacts to PyPI Test
+        if: inputs.deploy-to == 'PypiTest'
+        uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # pypa/gh-action-pypi-publish@release/v1
+        with:
+          repository-url: https://test.pypi.org/legacy/
+
+      - name: Publish artifacts to PyPI Prod
+        if: inputs.deploy-to == 'PypiProd' || github.event_name == 'push'
+        uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # pypa/gh-action-pypi-publish@release/v1

dbt_autofix-0.0.0.post1.dev0/.github/workflows/schedule.yml

@@ -0,0 +1,17 @@
+name: Run Nox every hour to check JSON schema parsing
+
+on:
+  schedule:
+    - cron: '0 * * * *'
+
+jobs:
+  nox:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # actions/checkout@v4
+      - name: Install uv
+        uses: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86 # astral-sh/setup-uv@v5
+      - uses: fjwillemsen/setup-nox2@da319daa4a57af7b0802d65173dd08b7e902fa08 # fjwillemsen/setup-nox2@v4.0.0
+      - run: nox --session check_latest_schema-3.13
+      - run: uv sync --all-extras --all-packages --python 3.13
+      - run: uv run --python 3.13 pytest

dbt_autofix-0.0.0.post1.dev0/.github/workflows/uv-dependency-submission.yml

@@ -0,0 +1,30 @@
+name: Dependency Submission for uv
+
+on:
+  workflow_dispatch:
+  push:
+    branches: ['main', 'master']
+    paths:
+      - '**/uv.lock'
+
+permissions: {}
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  dependency-submission:
+    name: Submit uv dependencies
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+    permissions:
+      contents: write # needs to submit dependency graph data
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          persist-credentials: false
+
+      - name: Submit dependency snapshot
+        uses: rmuir/uv-dependency-submission@1c48aaac13e566e39fd04269ff1900b86c1105c5 # v1.0.0

dbt_autofix-0.0.0.post1.dev0/.gitignore

@@ -0,0 +1,30 @@
+# Python-generated files
+__pycache__/
+*.py[oc]
+build/
+dist/
+wheels/
+*.egg-info
+
+# Virtual environments
+.venv
+.nox
+venv
+
+# IDE files
+.vscode/launch.json
+.vscode/settings.json
+
+# special files
+config_resources.csv
+project2/*
+
+.DS_Store
+
+# raw package hub output (because big)
+src/dbt_autofix/packages/scripts/output/*
+# profiles.yml temporarily added by unit tests
+tests/integration_tests/package_upgrades/dbt_utils_package_lookup_map_2/profiles.yml
+
+# Fusion logs output
+**/logs/*

dbt_autofix-0.0.0.post1.dev0/.pre-commit-config.yaml

@@ -0,0 +1,19 @@
+repos:
+- repo: https://github.com/astral-sh/ruff-pre-commit
+  # Ruff version.
+  rev: v0.11.2
+  hooks:
+    # Run the linter.
+    - id: ruff
+      args: [ --fix ]
+    # Run the formatter.
+    - id: ruff-format
+
+- repo: local
+  hooks:
+    - id: ty
+      name: Run ty type checker
+      entry: uv run ty check .
+      language: system
+      types: [python]
+      pass_filenames: false # Prevents passing only staged files, runs on the whole project

dbt_autofix-0.0.0.post1.dev0/.pre-commit-hooks.yaml

@@ -0,0 +1,13 @@
+- id: dbt-autofix-check
+  name: Check for dbt deprecations
+  description: Check for dbt deprecations using dbt-autofix (dry-run mode)
+  entry: python -m pre_commit_hooks.check_deprecations --dry-run
+  language: python
+  pass_filenames: true
+
+- id: dbt-autofix-fix
+  name: Fix dbt deprecations
+  description: Automatically fix dbt deprecations using dbt-autofix
+  entry: python -m pre_commit_hooks.check_deprecations
+  language: python
+  pass_filenames: true

dbt_autofix-0.0.0.post1.dev0/.python-version

@@ -0,0 +1 @@
+3.10

dbt_autofix-0.0.0.post1.dev0/AGENTS.md

@@ -0,0 +1,72 @@
+# `AGENTS.md`
+
+## Goals
+
+1. Make a pre-existing dbt project compatible with the new authoring layer, so it can parse and compile successfully on the Fusion engine.  
+2. Preserve existing functionality as much as possible.
+3. Flag when the dbt project is using functionality that's not yet supported in Fusion, and ask users so they can choose whether to wait for feature support or remove use of unsupported features. 
+
+
+## Migrating to the new authoring layer and the dbt Fusion engine
+
+if a user says "migrate my dbt project to the new authoring layer" or "make my dbt project compatible with the Fusion engine" do the following steps and the migration is only successfully completed once `dbtf compile` finishes with 0 errors. Create a changes_made.md file documenting and summarizing all of the code changes made in the user's dbt project, including what the error was, the fix applied, and a summary of why the fix was chosen.
+
+Before you begin, please read and understand the resources section below. You should strictly use the resources below to update the project.
+
+1. Run `dbtf debug` in the terminal to check their data platform connections. Proceed to step 2 if there are no errors. If there are errors, please summarize the error succinctly so the user knows how to debug on their own.
+2. Run `dbtf parse --show-all-deprecations` in the terminal to check for compatibility errors in their current project. Summarize the log output by specifying how many errors were found and group the errors in a way that's easily understandable.
+3. Install [dbt-autofix](https://github.com/dbt-labs/dbt-autofix) and run autofix to try to fix errors. Prefer uv/uvx to install (`uv tool install dbt-autofix`) and run the package (`uvx dbt-autofix deprecations`), but fall back to pip and other methods if needed. Summarize the results of the autofix run and include how many errors were resolved. Run `dbtf parse` again to check for remaining errors and summarize with how many errors were found and a brief summary of the types of errors.
+4. For remaining errors, please ONLY use the resources below to attempt to resolve them. If you can't figure out a fix from the resources below, notify the user and break out of the flow. Attempt the fixes error by error, grouping similar errors based on the error code and message. You should also summarize which error you're working on in the chat to give users context. 
+
+   **Special handling for common unsupported features:**
+   - **Python model errors**: Disable with `{{ config(enabled=false) }}` at the top of the file.
+   
+   Run `dbtf parse` throughout this step to check for progress towards completing the migration. Once `dbtf parse` finishes successfully with 0 errors, proceed to step 5. 
+5. Run `dbtf compile` in the terminal and check if it finishes with 0 errors. If it finishes with 0 errors, you have successfully completed the migration. If there are unresolved errors, try step 4 again. Except this time, use `dbtf compile` to check for progress towards completing the migration.
+
+## Don't Do These Things
+1. At any point, if you run into a feature that's not yet supported on Fusion (not a deprecation!), please let the user know instead of trying to resolve it. Give the user the choice of removing the feature or manually addressing it themselves.
+
+## Handling Unsupported Features
+
+When you encounter unsupported features in Fusion, follow this decision tree:
+
+### For Unsupported Model Types (Python models, etc.)
+- **Python models**: Disable with `{{ config(enabled=false) }}` at the top of the file
+- **Materialized views/Dynamic tables**: Disable with `{{ config(enabled=false) }}` at the top of the file
+
+### For Unsupported Config Keys
+- **Custom configs**: Move to `meta` block in model files (see [`custom_configuration.md`](https://github.com/dbt-labs/dbt-autofix/blob/main/manual_fixes/custom_configuration.md))
+- **Deprecated configs**: Follow misspelled_config_keys.md guidance
+
+### For Dependency Issues
+- If a model depends on an unsupported feature, disable the dependent model as well
+- Update exposure dependencies to remove references to disabled models
+
+## Resources
+
+### Common problems that cannot be addressed with deterministic dbt-autofix
+Use the files in the `manual_fixes/` directory as the context for resolving these common problems:
+- Each file outlines one problem and the solution you should use.
+- Only follow what's specified in the file. If you need more context, use the dbt docs section below as a resource.
+
+Unsupported features and blockers to Fusion compatibility. These pages outline the supported and unsupported features of the Fusion engine: 
+- https://docs.getdbt.com/docs/fusion/supported-features
+- Unsupported features on Fusion: https://docs.getdbt.com/docs/fusion/supported-features#limitations
+- https://docs.getdbt.com/docs/dbt-versions/core-upgrade/upgrading-to-fusion
+- If a model type is unsupported on Fusion (e.g. python models), you can disable it with this jinja macro `{{ config(enabled=false) }}` at the top of the file to disable the model.
+
+Config keys that Fusion should recognize: 
+You can find the latest schema file using this template: `https://public.cdn.getdbt.com/fs/schemas/fs-schema-{RESOURCE}-{VERSION}.json`
+- `RESOURCE` is either `dbt-yaml-files` or `dbt-project`
+- `VERSION` is the fusion version (e.g. `v2.0.0-beta.34`, but `https://public.cdn.getdbt.com/fs/latest.json` gives you the latest version)
+- Example file: https://public.cdn.getdbt.com/fs/schemas/fs-schema-dbt-yaml-files-v2.0.0-beta.34.json
+
+### dbt docs
+
+https://docs.getdbt.com/reference/deprecations#list-of-deprecation-warnings
+https://github.com/dbt-labs/dbt-fusion/discussions/401
+https://docs.getdbt.com/docs/fusion/supported-features
+https://docs.getdbt.com/docs/fusion/new-concepts
+
+

dbt_autofix-0.0.0.post1.dev0/CONTRIBUTING.md

@@ -0,0 +1,53 @@
+# Contributing to `dbt-autofix`
+
+## Installation
+
+This project uses `uv` for workspace and virtualenv management.
+
+1. Clone the repo: `gh repo clone dbt-labs/dbt-autofix`
+2. Install `uv`: [See docs](https://docs.astral.sh/uv/getting-started/installation/)
+3. Install dependencies: `uv sync`
+4. Activate virtual environment: `source .venv/bin/activate`
+
+You confirm your installation worked as expected via `dbt-autofix --version`
+
+## Testing
+
+The tests in this codebase are located in the `tests` directory and contain `integration_tests` and `unit_tests` subdirectories.
+
+To run all tests in the repo, simply run `pytest tests`
+
+Integration tests are based on check-in sample dbt projects and corresponding expected dbt projects and stdout log files. For example:
+* `integration_tests/dbt_projects/project1` is a sample input project.
+* `integration_tests/dbt_projects/project1_expected` is the expected resulting project after `dbt-autofix deprecations <flags>` is run.
+* `integration_tests/dbt_projects/project1_expected.stdout` contains the the expected stdout logs.
+
+If `*.stdout` files need to be updated to reflect new or changed logs as part of the change being introduced, run: 
+
+```sh
+GOLDIE_UPDATE=1 pytest tests/integration_tests
+```
+
+to automatically update the expected *.stdout files.
+## Adding new dependencies
+
+`dbt-autofix` declares `dependencies` as dynamic (managed by the `uv-dynamic-versioning` metadata hook), so `uv add` cannot write to `[project].dependencies`.
+
+- **Runtime dependency:** Manually add it to the `[tool.hatch.metadata.hooks.uv-dynamic-versioning].dependencies` list in `pyproject.toml`, then run `uv sync`.
+- **Dev/test dependency:** `uv add --optional test <package>` works as normal since `[project.optional-dependencies]` is static.
+
+## Releasing
+
+To kick off a new release: 
+1. Click into 'Releases' under the 'About' section of https://github.com/dbt-labs/dbt-autofix
+2. Click 'Draft a new release'
+3. Create a new tag - incrementing the last latest release available on https://pypi.org/project/dbt-autofix/ by either a minor or patch version as appropriate - format should be `v0.*.*`
+4. Title the release the same as the tag name from (3)
+5. Click 'Generate release notes` to populate the release body
+6. Hit 'Publish Release' ensuring that `Set as the latest release` is checked.
+
+That's it! The Github release triggers an automated release to pypi which can be observed at: https://github.com/dbt-labs/dbt-autofix/actions/workflows/release.yml
+
+## Troubleshooting
+
+If you're not getting autocomplete in VSCode for `dbt-fusion-package-tools`, open VSC settings and enable "Python > Terminal: Activate Env in Current Terminal."