.gitignore

__pycache__/
*.py[cod]
*.egg-info/
.DS_Store
Thumbs.db

# Local asset generators (they depend on the private herogen; only the rendered PNGs in docs/assets ship)
tests/assets/

# Docker test-env working dir: downloaded inputs (Marcie), round-trip outputs, server logs
data/

# local working dirs - never publish (logs and artifacts can carry paths and names from other work)
scratchpad/
.agents/

# example_workflows/ is a WORKING directory. Only one file in it is published today, nyc_skyline.png, and
# the graphs are still being built and tested against the nodes - they ship when their author says so, not
# because a blanket `git add` swept them up. Everything below keeps the renders, references and sidecars that
# accumulate while testing out of the repository.
#
# NOT *.png: nyc_skyline.png is the accuracy suite's source image (tests/accuracy reads it, ATTRIBUTION.md
# credits it) and it does ship, so a blanket picture rule here would be wrong. Renders that are NOT inputs
# get named one at a time instead.
example_workflows/output/
example_workflows/**/*.mp4
example_workflows/**/*.mov
example_workflows/**/*.exr

# The blanket render rules above stay: they exist to keep TEST renders from accumulating in a working
# directory, and that job is unchanged. What has changed since they were written is that the folder now
# publishes graphs, and a published graph is worth little without something to open beside it. So the
# deliverables are named one at a time, exactly as the comment above prescribes for renders that are not
# inputs: the first and last frame of each sequence, and the two review movies. A stray test render
# dropped anywhere else in the folder is still ignored.
!example_workflows/frames/
!example_workflows/frames/*.exr
!example_workflows/frames/*.mov
!example_workflows/acescct_native/
!example_workflows/acescct_native/*.exr
!example_workflows/acescct_native/*.mov
!example_workflows/acescct_native/*.mp4
probe.mp4
# A reference render brought in from Nuke to compare against, plus the sidecar our own writer drops beside a
# sequence. Named as a folder rather than by extension: a *.json rule here would also catch the graphs being
# worked on, and those are the author's to publish or not.
example_workflows/exr from nuke/
example_workflows/neon_cyborg_portrait.png