Skip to content

Ignore Julia environment and coverage artifacts - #13

Draft
smartalecH wants to merge 1 commit into
python/lengthscale-constraintsfrom
chore/gitignore-julia
Draft

Ignore Julia environment and coverage artifacts#13
smartalecH wants to merge 1 commit into
python/lengthscale-constraintsfrom
chore/gitignore-julia

Conversation

@smartalecH

Copy link
Copy Markdown
Collaborator

Stacked on #12 (base branch is python/lengthscale-constraints), which is itself stacked on #11.

Running Pkg.instantiate() in src/julia/SSP (or examples/julia) writes a Manifest.toml that currently shows up as untracked — easy to commit by accident, and a resolved manifest shouldn't be tracked for a package that supports a range of dependency versions. This adds a Julia section to .gitignore:

  • Manifest.toml and Manifest-v*.toml (Julia writes the versioned form for some julia versions);
  • *.jl.cov, *.jl.*.cov, *.jl.mem, left behind by julia --code-coverage and --track-allocation.

Verified by re-running Pkg.instantiate() in src/julia/SSP: the regenerated Manifest.toml no longer appears in git status, and git check-ignore -v attributes it to the new rule.

I deliberately left the PNGs that the examples write into the working directory (projection.png, constraint_sweep.png, ...) out of this — a blanket *.png rule would silently swallow figures we may later want to commit for the docs. Happy to add explicit names if you'd rather.

Running Pkg.instantiate() in src/julia/SSP or examples/julia writes a
Manifest.toml, which should not be tracked for a package. Also ignore the
coverage and allocation files that `julia --code-coverage` / `--track-allocation`
leave next to the sources.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant