I'm excited to introduce the #WARP Protocol – a protocol for commit messages It's a standardized commit message protocol that's set to revolutionize how we approach software development by enabling faster iteration cycles and increased reliability.
How does this differ from https://www.conventionalcommits.org/en/v1.0.0/ (which already has a robust software ecosystem), or the multitude of various "git standards/best practices" already in existence?
What about this "revolutionizes" software development or "enable" faster iteration, reliability beyond clear commits in any other form?
Author doesn’t appear to have heard of conventional commits at all, so this is pretty funny that it’s exactly the same thing with a very slight syntax.
They are all horrendous and useless and not actually used in production. If the inventor of these convential commit protocols don't have 7,000 commits they're framework sucks
First, WARP's focus is on speed and accelerating cycle time so it's flexible and not rigid. 2nd, defining the change to the exact module allows people to see what changes were made to what function or class. WARP has enabled me to acquire 7,143 contributions in half of a year with 100s of projects.
Ok I know what e/acc is but what the fuck is u/acc?