After giving them a 30min talk about the importance of proper commit hygiene and the dos and donts of git, I proceed to commit changes of different nature in 4 files as a single commit named "did stuff".

I lost all authority on the subject forever.

It’s Friday afternoon...

git add .
git commit -m “I forgot but I did stuff”
git push -f

@evilmupp3t If you've got slides & its okay, please share. I've never really thought about my commit process formally.

I'd love to have your thoughts.

@kunashe sorry, mate! I don't have any slides. But I can recommend a few articles that I used as a base:

Http://nvie.com/posts/...
Outlines (in an easy to understand way) a pretty simple but effective branching model if you work in a team.

As for commit hygiene, Eric merritts post is a good reference : http:///www.ericbmerritt.com/2011/...

@evilmupp3t yep that git.brancjing article is great - I used it to teach my colleagues in the last company I worked at how git works.

Oh and I can't click the second.link, would you mind posting it again?

@evilmupp3t repost the second link, it's unclickable

@evilmupp3t - thank you for the link to the branching article.

The Udacity Nanodegree team asks you to write really good commit messages.
But once I get on a roll, I keep fixing thongs and adding features and a commit is the last thing to do before taking a break. So it usually goes like: "feat: lot of stuff and some fixes"!

http://ericbmerritt.com/2011/09/...

There you go, @dsteiner, @tisila

@evilmupp3t thanks!

@evilmupp3t thanks! 😉