Skip to content

Conversation

@Flamefire
Copy link
Contributor

Contains common files created e.g. by IDEs (build folder) and by pip (/scorep.egg-info)

This avoids accidentally committing build artifacts and leads to less polluted git status output

Factored out from #68

Regarding comments:

This requires me to add the files I need to ignore to the repo (e.g. from eclipse)

You are not required to do this. If you are fine with git status showing your IDE files you don't need to do anything

which ends up in a total mess of files if any developer does this.

What mess? This is a text file and there are only some common files/folders which are recreated very frequently. The .gitignore file is meant to reduce the mess git status shows which will then show a clean working tree when it is clean (in terms of git)

adding e.g. /scorep.egg-info will prevent git clean -df from working "correctly", and removing all build files.

For that use case use git clean -dfx which does also remove ignored files

--> In summary it helps to focus on the important files especially when adding new ones

@AndreasGocht
Copy link
Collaborator

You are not required to do this. If you are fine with git status showing your IDE files you don't need to do anything

Let me put it the other way: I use to create my own .girtignore, ignoring itself and all files that I want to be ignored on my local machine. If there is a .gitignore in the project, I need to use this, which I might not want to.

For that use case use git clean -dfx which does also remove ignored files

But I want to keep the files of the 500 IDEs I am using 😀 .

--> In summary it helps to focus on the important files especially when adding new ones

True, but I think a local .gitignore is sufficient for that.

@Flamefire
Copy link
Contributor Author

True, but I think a local .gitignore is sufficient for that.

I agree with that although I find it beneficial to have one with the repo so when you clean checkout and work on it you don't end up having to set up everything again. Your workflow is unusual as in I haven't seen it before as all projects I've worked with have a .gitignore due to the above reasoning (checkout experience)

Anyway, your repo, your call ;)

@AndreasGocht
Copy link
Collaborator

I have to do a bit of research on this issue. I'll leave the PR open in the meanwhile.

Contains common files created e.g. by IDEs (build folder) and by pip
(/scorep.egg-info)

This avoids accidentally committing build artifacts and leads to less
polluted `git status` output
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.

2 participants