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.
Motivation and context:
Realized I needed to write a
.gitignore
for a new repo, so thought that it would be worth the extra few minutes to do it through Nengo Bones.How has this been tested?
Added to the Bones
.nengobones.yml
, generated a new.gitignore
.How long should this take to review?
Types of changes:
Checklist:
Still to do:
All-encompassing or minimal
Right now, I seeded this with Github's Python gitignore template, with some tools that we don't use take out and some tools that we do use added in. I haven't yet checked all downstream
.gitignores
for any additional things that would be generally useful. Before doing that (and writing tests, docs etc) I figured I would get some feedback on whether we want this style of.gitignore
, which has probably more things in there than we need, or if we want a stripped down minimal.gitignore
, which is what we have in most of our repos right now. The all-encompassing one should require fewer custom entries in.nengobones.yml
at the cost of more lines in the generated.gitignore
file.