52
wlan404
8y

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: πŸ‘ΏπŸ‘ΏπŸ‘ΏπŸ‘Ώ

Comments
  • 1
    Even better when you're passing the gitignore around
  • 0
    @Milenchy wait, it's bad to have gitignore in the repo? Why? When someone clones it he has to make his own gitignire?
  • 1
    @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
  • 0
    Thats why i make sure to commit .gitignore before commit any source code πŸ˜‚
  • 0
    /git blame 😈
  • 0
    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.
Add Comment