Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
netikras26367185dMy commit messages look very similar today :) Because I'm adding the GL CI/CD support, so.... kind of a rain of commits with miniature changes :D I'm already running out of unique commit messages
IntrusionCM6338185dCreate a branch.
Work till it works, tested and verified.
Cherry Pick and rebase on main branch commits from two.
While rebasing, edit the commit messages.
More work, yes. But frustration from not being able to fix stuff like you want to do leads mostly to "" bad documentation "".
So the cherry picking and rebasing makes sure that you take your time and think.
More than I'd like I suddenly realised whole rebasing that the commits have consequences I wasn't aware off.
webapp631185dCreate a new branch and squash these commits on merge.
devTea25684185dUse git hooks that appends your branch name on your commit so at least you know when and how this shit happened
Earu94184dI just usually append a version number to these kind of commits, some day the commit history may look like:
ScaryException2924170d@netikras feel you. when I created my first CI/CD configuration my commit messages have been like:
-removed stage prepare
-added stage prepare
-removed stage prepare because it breaks the build
-build is now succesfully broken without prepare
-changing snapshot because shit doesn't work