👏 Learn 👏 to 👏 squash 👏 those 👏 commits 👏
post
You don't just write your entire project, then make your first commit?
/j
Yeh I use git (git commit --amend)
git commit --amend --no-edit and git push --force-with-lease
No-edit skips opening an editor for the commit message and just reuses the same message.
Force-with-lease will force push but only if your local is not missing commits that remote has. Ie other people haven't pushed anything since you last pulled.
rebase & fixup or reset are your friends
I love editing history. Fix the bug in the change that introduced it!
Then force-push, and fuck up someone's day!
git branches are free
work in your tree
til the changes are ready
300 git push --force-with-lease a day and nobody mad
I prefer to force push directly to the production branch.
Skill issue
Yep. https://gitlab.com/bss03/halogen-lambda/-/commits/main
Not an issue, https://gitlab.com/bss03/type-aligned/-/commits/main
for real devs. https://gitlab.com/bss03/nested/-/commits/main
Is it humor because we make fun of you?
I cannot give you a 100% for consistency. You have three inconsistent check in messages: 'tet', 'FueraEstanciaRowRename', and 'Revert "test"'. You must be uniformly informative with your messages.
my private repo is filled with "stuff", "more stuff", "new stuff", "changes" commits.
Whenever I work on something, I don‘t intend on publishing, I use What the commit.
well yeah, in an enterprise project we would say "chore(test)". Semantic release ftw!
Small incremental changes are good.
top 50 comments