Starting a new project

Me: This time we'll follow all the best practices, do atomic commits and write meaningful commit messages.

Coworker: Yeah! Let's start.

40 commits later.

Me: Why is .idea folder in the repository?

Coworker: Sorry My Bad.

Me: 👿👿👿👿

Even better when you're passing the gitignore around

@Milenchy wait, it's bad to have gitignore in the repo? Why? When someone clones it he has to make his own gitignire?

@PRein It's fine the first time of course, but for us it happened in every commit lol. It was a university project so I didn't bother to tell them to fix their shit

Thats why i make sure to commit .gitignore before commit any source code 😂

/git blame 😈

Yes its best to add gitignore when creating the repo, that is what I generally do. But there are people who open a JavaScript file using R editor or gedit.

R adds a .r_history file and gedit creates swap files.

When I know people are going to use these editors I can add related files to gitignore.

But the whole situation can be avoided if before committing developers do a "git status" and add the files / directories to gitignore.