Create a `.gitignore` file
Issue #5
resolved
We should create an empty .gitignore file and start populating this with common files that we wish to ignore (such as temporary files, generated executables etc.).
Comments (12)
-
-
reporter
You could open a PR but we could wait a while before merging in case others want to contribute?
-
- changed milestone to 8.0.1
-
- changed status to resolved
Fixed in PR #13
-
- assigned issue to
-
- changed status to open
Re-opened as there's some build artefacts missing form the .gitignore that was merged into next
-
Yes, lots of stuff gets produced in tests, often executables without an obvious pattern. They might logically belong to in testing PRs.
-
-
Move gitignore lines from top-level to subfolder
This was done to avoid making the top-level gitignore messy as there are potentially lots of build artefacts in the 'tests' subdirectory. Also, this way the ignore is local to the thing being ignored which makes the statement itself less messy.
TODO - add more local gitignore files within 'tests' to ignore build artefacts generated by running 'make tests'
This addresses issue
#5→ <<cset 267c15bc399c>>
-
Add build artefacts of 'make tests' to gitignore
This is done in subfolders to avoid making the top-level gitignore messy as there are potentially lots of build artefacts in the 'tests' subdirectory. Also, this way the ignore is local to the thing being ignored which makes the statement itself less messy.
This addresses issue
#5→ <<cset d96ae7bba382>>
-
Is this resolved now PR #16 is merged?
-
- changed status to resolved
Resolved by PR #16
- Log in to comment
I've made a first iteration of this in the gitignore branch. Shall I make a PR to merge something right away, or should we let it build up in a branch?