today I pull a project to take over from my colleague
today I notice all commits where on master branch
today I leave this world T_T

Leave the world = commit -m 'suicide' ?

@ThatDude I wish I can. but in his defense, the project will be rewritten to native languages so I don't give a shit what happens to this repo, I will happily delete it once we finish transforming it :D

@Jakuho pretty much that :P

@Jakuho more like:
@gitpush hell
git commit -m “yep reached hell”
😂😂

@ThatDude 😨😨 I forgot commit comes before push 😂😂😂😂😂

@Electrux see why we git hate you -.- :P
@Thatdude we must complete the army :P (I"m so taken away with WOT and Armored warfare :P)

@gitpush naw I know u love me ❤️❤️ 😂😂😌😌

@Electrux 😓😛

Well, what's the problem when he worked alone on this project and no CI was running? As long as the commits are correct and have a good description

@Fenix in his defense, yes commit messages are clear af. but when I gave him repo url, I gave him full git command:
git clone xyz -b dev

I commit in master all the time... As it seems any solo projects I make are only written by me, no one else usually pulls unless it's actually working and they need it

Sounds like your guy?

@billgates for solo projects it can be ok, but for work projects it shouldn't ...

@gitpush these solo projects are at work. It's just that I'm very likely to commit everything

@billgates the only reason that I prefer to have dev and master because here out of a sudden we will be asked for a release when it wasn't even planned, so having a master branch with everything tested (even if solo project) will save us a lot of headache

@gitpush sounds like you have a problem with release planning then.
I also commit directly on master (there is a prod branch I push to whenever I release), and release don't happen "all of a sudden", only when master is deemed stable and in a releasable state.
Any hot-fix is also done on master, and cherry-picked on prod branch before being released.

@Fradow "sounds like"? be 1000000% sure :\

@gitpush At least you are aware of it! I'm careful because a lot of people are not even aware of that.
Good luck convincing stakeholders that releasing whenever they want is not a good business practice. Or selling them on "Move fast, break fast", emphazing on the breaking on production part.

@Fradow we tried but its just the way they think is strange, they don't care about that and they end up blaming us. Our PM sometimes fights with them because they keep on blaming us when we warned them a million times about it

@Fradow @gitpush well for my solo projects release planning is:

Not Done, Done and you can now pull if you want to... or even care that I wrote a program that automates this boring thing u do mentally