Small Fixes
Added 1800 new lines...
this post was submitted on 03 Jul 2023
67 points (100.0% liked)
Git
29 readers
1 users here now
Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
Resources
Rules
- Follow programming.dev rules
- Be excellent to each other, no hostility towards users for any reason
- No spam of tools/companies/advertisements. It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.
Git Logo by Jason Long is licensed under the Creative Commons Attribution 3.0 Unported License.
founded 1 year ago
MODERATORS
Hey, no one ever asked for the quantity of small fixes :3
Legit I would be okay with that if it was closing a test gap and the changes in the source directory were clarity and documentation
One senior guy managed to merge with the commit template, as is, with **Insert brief summary here** and **description goes here**
"A dumbass committed her email address hardcoded as a recipient for all mails, again."
-- Me, the dumbass
Its all fun and games until the email list doesn't include the people its supposed to and I get a call on a text on Sunday morning because 'Ahmahgad the etl pipeline hasn't started!?!?!'
"fix ci" "Again" "Maybe?"
Every time I work on CIs I just lose it after 1 or 2 commits and squash merge later on. Also when integrating projects together (eg I'm working on a language and made a POC for a new parser in a separate project) I'm just like "hajzjgkzlabai yes"
I know I'm having a bad day when my commit messages have question marks in them.
You can tell when I've started to lose hope when my commits start becoming "Probably won't fix CI"
git commit -m 'oops'
Two users trying to chat with each other via commit messages.
1: "Youtube bro" 2: "Ohoo thanks"
Empty commit message. Yes it's possible. Yes it's as bad as the cli tries to prevent it
I just pushed "idefk", cause frankly, no idea what was in it, but it touched half the repo
I use a single dot when committing to a feature branch. I will either rebase or merge --squash anyway, so what's the point really.
e: in my private projects that is, I use a jira ticket number at work, because I have to.
Hehe I do the same, just a dot
For personal stuff especially when I use git just to sync between laptop and computer most of my commits are the things that don't work and I use for new stuff ~for changes and X for broken stuff.
So a commit can be " + new feature ~logging to accommodate new feature X Edge case crashes the new feature."
Accurate
Worst commit that i pushed receantly was git commit -m "._." for my personal js practice repo.
I needed it because all of the content is "CRLF" but I'm using "LF" on my machine.
Probably anything saying "Commit" as the main verb (apart from "Initial commit"). "Add some code" is annoying but "Commit some code" is so much worse to me. Yeah, of course, every commit is committing some code lol.
Honestly this is the area I feel separates junior from senior devs in quite significant ways.... on both extremes.
I hate having to go through a bunch of "fix, fix, typo, syntax, fix, thing, foo" comments when trying to review the history of a file....
Similarly commits that describe which files are being touched and in what way are just as bad.
Gimme the why for that commits existence please... not just what I can already tell by looking at the file stats.
"Stuff" or "🤫"
Me on feature branches when I have weird CI issues: “floopie 7”. You can guess what the previous ones are. Yes I’m aware of amend but this is easier and I just iron that stuff out when I fixed my problems
Debug
Degug
Debugging
Itdiydigxigxjxutxu
Debug
189cbca refactor
425b7de increased bullshitry levels
33bc72d works on my machine
f5fe8ed who the fuck cares
112e7ff probably did more shit
c02191c updater cool factor
view more: next ›