Your local secrets and generated artifacts stay out of Git via .gitignore (repo root) and dab/.gitignore.
From the repo root:
git status --ignored --short | grep '^!!'Or verbose rule match for one file:
git check-ignore -v scripts/databricks_config.env| Pattern | Why |
|---|---|
scripts/databricks_config.env |
Your workspace paths, warehouse ID, optional tokens — never commit |
*.env |
Any other env file with secrets |
!*.example.env |
Exception: template files like scripts/databricks_config.example.env are tracked |
.venv/, python/.venv/ |
Local Python environments |
.venv-notebooks/ |
Optional notebook tooling venv |
data/overture/ |
Downloaded Overture data (large) |
simulation_output/ |
Local sim output |
python/dist/, python/build/, *.egg-info/ |
Wheel / setuptools build |
__pycache__/, .pytest_cache/ |
Python / pytest caches |
cache/ |
Generic cache dir |
dab/.databricks/ |
Databricks CLI bundle state |
archive/ |
Local archives |
.vscode/settings.json, .claude/settings.local.json |
Machine-local IDE settings |
.DS_Store |
macOS metadata |
| Pattern | Why |
|---|---|
.databricks |
Bundle deploy state under dab/ |
resources/*.bundle_skip |
Temporary rename when SDP_SKIP_APP=1 deploy stashes the app YAML |
cp scripts/databricks_config.example.env scripts/databricks_config.env
# Edit databricks_config.env — it remains untrackedReview .claude/settings.json before pushing — it references internal plugin IDs. For a fully public repo you may want to stop tracking it (add .claude/ to .gitignore and remove from Git history) or replace with a neutral placeholder.