Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this is useful for developers that init a gleam project into an existing git repo where the
gleam new
tool will refrain from populating the .gitignore file. This situation may occur for users of devenv.nix or flake.nix.Reasons for making this change:
There is no clear way to force the
gleam new
CLI tool to populate a valid .gitignore when running the CLI tool from inside a git repo. Since I manage my build tooling with devenv.nix which already spawns a git repo, I needed a different way to figure out how to get a sufficiently decent default .gitignore for my Gleam project. As I didn't find anything or any relevant open PR (searched for any PR matching the filter:gleam
) to inform this, I reckoned that having this recorded in the .gitignore repo provides folks a reference in case they run into a similar problem.Links to documentation supporting these rule changes:
gleam new
which includes the .gitignoregleam new
tool populates