There’s no such thing as a private repository.

Even if no one else will ever be working on said project, you might in a year or so. Do yourself a favour and write a decent message.

Also, what if you decide that this pet project is actually cool enough to release it to the public? Your fellow contributors will really, um… dislike your message of a plain ..

Just go ahead and create clean commits and meaningful commit messages.

You never work alone on private projects. You work with future you.

I guess that says everything. I keep my commit messages clean, as if I were a team member. I also keep my commit contents clean, trying not to leave debug lines or TODO comments that can be solved fast.

Always code like the next person who will maintain it is a maniac psychopath who knows your address. — Unknown

Thank for A2A

I have a habit of writing proper commit messages, doesn't matter the repo is private or it has minor changes. Commits help in achieving traceability, understanding the flow in both backward and forward direction. Btw what productive will you do in five secs you save by not writing the message. Make a practice. It won't bother you anymore.

Yes Mev-Rael, you are not alone in this. I too write git commit -m "." and also git commit -m "Initial commit" , git commit -m "2nd commit" and so on :P

Once I decided to follow a principle, the observance of that principle is for myself, not for anyone else. So, when I commit, I always try to:

• keep the changes small enough to affect to only one purpose
• take a short note about that purpose

I used to prefix these words before any commit message:

feat:"This feature has been added"

chore:"For code maintenance/refactor"

test:"Any test cases added

fix:"Any major fixes"

docs:"Any documentation"

style:"css style changes"

Mostly following the principles of How to write Git Commit messages paired with Alfred Snippets for emoji commit messages.

Started this a few years ago and now it's totally natural for me to write clean commit messages.

However downsides of this is, that if you see some ungly commit messages, you get a baaaaad feeling bout it.

The same as in profesional, a descriptive of what i done

1- git commit -m "05 march 2017 "

2- git commit -m "Second commit "

3- 2- git commit -m "Today task done "

I write the changes that happened as if someone else would read it mainly to keep me used to having to summarise what happened in the commit so that I can get better at that for my work projects.

Usually when i'm working on my own projects my commits going like :

git commit -m "Hello"
git commit -m "Okay"
git commit -m "Huh"

But when it's related to issue fixed it's like :

git commit -m "Fixing Shity Style"
git commit -m "Fixed Seeds"

Kinda summarizing what has been said, but I would definitely try to write meaningful commit messages for the following reasons:

1. The project may end up being team based in the future. You never know.
2. Git is your source code's history, so just think about your future self looking back on your code and wondering what a certain commit actually did.

And obviously if your code is open sourced, you would want others to be able to know what is going on.

Gg i work on different pcs so some commit messages are "tmp commit" ;D ... but usually i try to stick to "does blabla to blubb" just so I can guess what I was doing 2 years ago ...

Well, one day you're gonna look back and wonder what your commit was about. It doesn't really take a lot of effort to briefly summarize what you did, no? My commit messages are exactly the same for both my private and public repositories.

Im disciplined. I imagine myself in a year or two as another team member :)

For me, it is git commit -m "Minor changes"

wip

:)