That’s why I’ve got my IDE configured to make a commit and push for every single ctrl-s.
And one more thing, I’m not going to squash before my final PR.
EDIT:
For those of you interested, here’s my gitconfig alias to help with this workflow:
[alias] ctrl-s-commit-push="!f() { count=$(cat count.txt); git add .; git commit -m \"$(date): commit $count\"; git push;}; f"
IMPORTANT: For those who are downvoting, yes, my entire comment is sarcasm, lol! Do not ever do anything like this in a shared repo, ever! If you actually do this in a shared repo, your access will likely be revoked the moment someone sane and competent realizes what you’re doing.
Addendum: In that alias, I would’ve used left angle bracket instead of
cat
, but apparently lemmy scrubs those. I even tried the entity for it, but no go for either.And one more thing, I’m not going to squash before my final PR.
Pure evil.
Wouldn’t that mean you just have shit tons of commits? What about the commit message?
“Hit Ctrl-S”
Timestamp would suffice
That sounds just awful. But ok.
I disagree.
Be…before I go. Could you approve all my experimental PRs?
Real story, I have a branch that’s been open for four years at my company to add support for nested postgres transactions. It works flawlessly… but we, the senior devs, are uncertain if it’s a power that would be used responsibly by the juniors. If I’m going to walk into the light, I’m going to make sure there’s a badass explosion behind me.
I’ve got one for a vscode feature (middle mouse click for go-to definition) that I want but the maintainers don’t think it would be used.
Godspeed my friend. 10/10 I would use that irresponsibly.
*commits
ERROR: There are 5000 conflicts, please resolve them before pushing
You haven’t written your unit tests and you have 675 compiling errors left. It’s time to sleep grandpa
RIP
It’s too late.