well yeah, in an enterprise project we would say "chore(test)". Semantic release ftw!
this post was submitted on 23 Jun 2026
86 points (92.2% liked)
Programmer Humor
31948 readers
379 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 3 years ago
MODERATORS
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.
[Test] around and find out
You don't just write your entire project, then make your first commit?
/j
I do kinda do that with the initial commit (don't commit anything until I have something really basic that works). It feels awkward to commit code that does nothing.
That's all I ever commit
👏 Learn 👏 to 👏 squash 👏 those 👏 commits 👏
Seriously. My colleague does the same shit and it made me so mad until I realised he was on his branch. Then I was like, whatever, as long as you do a proper MR.
You need to learn refactoring/squashing
A dev on windows? Of course that's your git log!
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
Continuous integration is better. Fight me
Nothing about continuous integration prevents you from using a branch to prepare your changes.
Yes, if you use feature branches its literally not continuous. It’s adjacent though.
Continuous Integration is a software development practice where each member of a team merges their changes into a codebase together with their colleagues changes at least daily
Meaning everything is in a version controlled mainline
People disagree about what CI is, but that’s the definition i subscribe to
So does everyone work directly on main all the time? Do all of you work on the same project or are there multiple with one person per project? How do you work around the broken code your coworker just pushed so you can finish your tasks?
Yea you always work on main on the same project.
You don’t push broken code. You always need to keep mainline healthy
It takes some special considerations, but the benefits are great.
That doesn't stop you from removing your test commits before pushing
so when something breaks both devs, the one who made the previous change and the person pushing new, have to work together to solve the issue? no PRs or is everything a fork? do you revert and rebase every change?
You revert the broken commit usually.
https://martinfowler.com/articles/continuousIntegration.html
This is a good article on the topic
I personally make feature files. So if i'm working on FactorySeederModemLookupVector.ts someone elses could work on ☝️🥵🙏.php without bothering each other. Tho, my collabs have been ones with a LOT of communication.
load more comments
(2 replies)
load more comments
(15 replies)
Looks like a normal branch where someone debugs some GitHub workflow.
Me when learning GH Actions/CI/CD
I see I'm not the only one fighting with CI/CD pipelines.
nonsense, I would never use windows
view more: next ›