Fucking hate it when I have to stop coding and commit in the middle of some function, always end with some weird commit message

Why would you commit in the middle of a function?

@DoctorWhatIf for example if I have to leave immediately otherwise I miss the train, I work in neighbour city

@Gostwow but if you're halfway through writing something, why commit unfinished work then?
To me it sounds worse than just leaving it uncommitted until finished.

@DoctorWhatIf just to git pull when I get home and finish it but you're right in some situations it's better not to

@Gostwow oh, OK, if you're going to follow up on it it's understandable.
But I would then (seeing as you're using gut) just write something like "work in progress - feature A" and then amend the commit later with a proper message, when the work was actually done.

@DoctorWhatIf that's actually a pretty good idea, didn't think of it

@Gostwow well, glad I could help 😉

@Gostwow also, git rebase -i is your friend if you have older commits like those you want to prettify.

For feature branches I own, I often just comment with "wip" for "work in progress" and then I either just "git commit -amend" to rewrite that message.

Sometimes, I have loads of wip commits that I just squash into one once the feature is complete; and it's helpful that both github and bitbucket allow to merge a pull request using a squash strategy so that juniors and beginner can feel confident about just committing one commit back to master.

@k0pernikus out of curiosity, have you ever had situations (especially with the aforementioned junior developers) where squashing pull requests like that resulted in got weirdness (duplicated commits, etc.)?