There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

lil ,
@lil@lemy.lol avatar

You should not use -m, you should write commit body!

SirQuackTheDuck ,

Nah, most commits don’t need a body

zalgotext ,

Why? My coworkers are barely literate and won’t read anything with more than 4 or 5 words, writing a commit body would be a waste of time.

pete_the_cat ,

For me, it was my boss gave me a programming task which he knew would take hours or a day or two… and then 15 minutes later tells me to “switch focus” and do a menial task that any of my five coworkers could do 🤦‍♂️

giggling_engine ,
@giggling_engine@lemmy.world avatar

The usual reason would be “because coworkers”

lemmesay ,
@lemmesay@discuss.tchncs.de avatar

[conventional commits] (www.conventionalcommits.org/en/v1.0.0/) will save you.
or maybe commitizen if you’d like not to write them by hand.
and maybe commit and tag version, which will create changelogs for you of you follow semver

KeepFlying ,

“stuff”

nomecks ,

“Commit”

catastrophicblues ,

Oh god I feel so called out. I wish I paid more attention to my commit messages but I’m usually too busy fixing the directory structure and refactoring. Sigh.

brlemworld ,

My company collapses into a single commit at merge so idgaf what the commit message is anymore. Though I would prefer not collapsing them.

DoomBot5 ,

Master should just have the feature description commits, not the hundred commits it took to get there after refactoring the code for the 3rd time and pulling changes from master since it’s taken so long to get done.

catastrophicblues ,

Yeah I worked at a place like that, but it made sense because we were also expected to keep PRs small, so a good commit message for several squashed ones was perfectly fine.

GyozaPower ,

I prefer that approach. We work with smaller tasks, so it makea more sense, plus it helps keep the master clean and if you want a more detailed view of the specific commits, you just have to click on the link to the PR. It’s a better way to organise it IMO

EmperorHenry ,
@EmperorHenry@discuss.tchncs.de avatar

reminds me of what youtube was doing to firefox users for awhile.

hypnotic_nerd OP ,
@hypnotic_nerd@programming.dev avatar

git commit -m “break codec sync if UA = firefox/gecko”

paul ,

do git commit -v and then just summarize the diff you have in your editor in a human readable form.

KeepFlying ,

Don’t just summarize the content though, summarize the rationale or how things connect. I can read your diff myself to see what changed, I want to know the logical connections, the reason you did X and not Y, etc.

Or just say “stuff” and provide that context in the PR description separately, no need to overdo the commit log on a feature branch if you’re using squash merges from your PR.

deadbeef79000 ,

P1000x this.

I can read a diff.

I need to know why.

No, a code comment isn’t good enough, it’s out of date after the next commit.

KeepFlying ,

Code comments for "why"s that persist. Commits for why’s that are temporary.

If you need to run X before Y, add a comment. If you added X before why because it was easier, leave it in a commit

deadbeef79000 ,

If you need to run X before Y…

Add a test that asserts that.

Pacmanlives ,

git commit -m “changed somethings “

git push origin master

jelloeater85 ,
@jelloeater85@lemmy.world avatar

Do you always have to do origin master? I’ve seen it where sometimes just git push works and other times not.

Meowoem ,

I think it depends what branch your local version of the repo is set to. If you’re already in master then it’ll push there, if you’re in a testing branch then you can push it straight to master instead by telling it to

jelloeater85 ,
@jelloeater85@lemmy.world avatar

I just meant it not auto creating a new matching named branch.

adrian783 ,

uh in any actual company you almost never push to origin master. so I think it’s a joke.

MajorHavoc ,

Not with that attitude! /s

jelloeater85 ,
@jelloeater85@lemmy.world avatar

Force push Fridays!

Valmond ,

Depends on the configuration right?

You can work on your branch and then push that to integration for example.

I mean you’re not working on your local master/main branch right?

herrvogel ,

In most actually companies you can try push to origin master, but it’ll likely get rejected by the repo’s security policies.

TheUncannyObserver ,

That’s part of the joke, I think. If it’s a repo more than just you use, you would almost never push directly to the main branch.

zcoyle ,

where it Just Works, the branch is set up to track a remote branch

git-scm.com/book/…/Git-Branching-Remote-Branches

MajorHavoc ,

I was being more evil than that, saying that if one is gonna push direct to main, might as well maximize the possible damage to everyone else’s branch.

jelloeater85 ,
@jelloeater85@lemmy.world avatar

Lol why not just delete the whole project from GitHub… I mean, everyone has a copy, right?😱

Valmond ,

push origin your/branch

Pushes, you guessed it, your/branch!

Head is usually your checked out working branch if you’re not in a headless state, right?

jelloeater85 ,
@jelloeater85@lemmy.world avatar

Force push main, straight to jail🤣

Yup yup, usually you’re on a branch, sometimes a tag. I mean it’s all just pointers to references at the end of the day. I tend to treat Git like a story book, some folks still act like it’s SVN.

sloppy_diffuser ,

git-scm.com/docs/git-push#Documentation/git-push.…

jelloeater85 ,
@jelloeater85@lemmy.world avatar

I tired that, still was having issues, weeeird.

MajorHavoc ,

You forgot this –force flag.

Valmond ,

I’m too lazy, I use -f

Looboer ,

Just use What The Commit.

You can also create a git alias:

git config --global alias.yolo ‘!git add -A && git commit -m “$(curl --silent --fail whatthecommit.com/index.txt)”’

Now you can just type ‘git yolo’ to create a commit!

hypnotic_nerd OP ,
@hypnotic_nerd@programming.dev avatar

Well such an informative reply! Thanks mate 👍

ikidd ,
@ikidd@lemmy.world avatar

Full send.

Olgratin_Magmatoe ,

“Make Sure You Are Square With Your God Before Trying To Merge This”

MajorHavoc ,

Well that’s about half my commit messages that are going to be nonsense on weekends projects, now. Thank you!

hakunawazo ,

“Chuck Norris Emailed Me This Patch… I’m Not Going To Question It”

_dev_null ,
@_dev_null@lemmy.zxcvn.xyz avatar

My first script ever was written in lua for a world of warcraft macro to spit out chuck norris one liners. People in the barrens hated me.

jungle ,

Thanks for that, I’ve been laughing like a little kid:

“hoo boy”

“lol”

“Become a programmer, they said. It’ll be fun, they said.”

I can feel those so well! :')

rustydrd ,
@rustydrd@sh.itjust.works avatar

“blah”

CarbonScored ,
@CarbonScored@hexbear.net avatar

Forward three hours, me using thesaurus.com to try fit the whole gist of my change into the first line.

crackajack ,

That’s in any bloody workplace! Especially if there is o synergy between different teams.

aes ,

Psst,

git add -p

Johanno ,

What does this?

foxymulder ,
@foxymulder@lemmy.ml avatar

“patch mode” - Patch mode allows you to stage parts of a changed file, instead of the entire file. This allows you to make concise, well-crafted commits that make for an easier to read history.

pomodoro_longbreak ,
@pomodoro_longbreak@sh.itjust.works avatar

Highly recommend throwing –patch on any git commands you’re used to using. You will have the prettiest, most atomic fkn commit, I’m serious people will love you for it.

I mean many people won’t care, but the quality folk will notice and approve.

oce ,
@oce@jlai.lu avatar

Or just use a good IDE that makes doing atomic commits pretty natural.

pomodoro_longbreak ,
@pomodoro_longbreak@sh.itjust.works avatar

I’ve only tried the VS code hunk stager thing, and found it cumbersome compared to command line, but if you can make a GUI work for you ya go for it. I’ve never found it worth the trouble personally

dukk ,

Shout out to Lazygit for letting me stage individual lines

pomodoro_longbreak ,
@pomodoro_longbreak@sh.itjust.works avatar

Looks pretty neat. I like that it shows the commands it’s issuing!

oce ,
@oce@jlai.lu avatar

You should try the JetBrains IDEs, as the other said, you can pick changes line by line graphically, when you commit, when you do a diff with another branch or when you fix conflicts. It’s much more convenient than commands and terminal text editors.

Johanno ,

We make a singular commit per feature.

pomodoro_longbreak ,
@pomodoro_longbreak@sh.itjust.works avatar

Trunk based, eh? Yeah, we do that on a couple teams where I’m at, too. I like the philosophy, but force pushing the same commit over and over as you’re incorporating review feedback is antisocial, especially when you’ve got devs trying to test your changes out on their machines.

Omgpwnies ,

eh, just squash and merge. Feature branch can be messy as long as main is clean

Johanno ,

Yep. You have to make sure your feature branch works.

KairuByte ,

I always find this hard to follow personally.

AnarchistArtificer ,

Yay, learning!

dukk ,

Better yet, git commit -p

sip ,

uuuuuuuu. and you could do -m to describe the commit.

next they’ll add --push/-P.

perhaps add -r for fetch/rebase then commit.

one command to rule them all! 😈

syd ,
@syd@lemy.lol avatar

I’m using Copilot for it right now. It works on half of the cases.

mdurell ,

That’s about 300% better than my average!

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • random
  • [email protected]
  • lifeLocal
  • goranko
  • All magazines
    •