VP of DevRel RapidAPI ❯ Award-winning Web Developer NodeCLI.com ❯ Google Dev Expert Web tech ❯ 2x GitHub Stars Award ❯ WordPress Core Dev ❯ TEDx Speaker ❯ "awesome example for devs" — Satya Nadella
Location
San Francisco Bay Area
Education
EE-CS Engineer turned Software Developer
Work
VP of DevRel (DX Eng., Content & Community) RapidAPI ❯ Google Dev Expert ❯ GitHub Star ❯ NodeCLI.com
You folks are right!
You're right. After sharing this, what was meant to be a personal workflow, I ended up in long debates on Fb/Twitter about how this can be improved.
Here's what we end with
git push --force-with-lease
as shared here above (updated the post) dev.to/mrahmadawais/one-command-to...But I am still not satisfied, so I am building a git hooks based workflow to make sure no bad git commit message gets committed in the first place.
Thanks for mentioning that though. Peace! ✌️
If you are using a development environment that is integrated with git,
--force-with-lease
can have the exact same problems as--force