How do you write git commits? For example if you have fixed a bug do you write "Fixed a bug where..." Or "Bug fix for...

OwO what's this?

git commit -m “here is my commit message”

imperative:

“fix bug in myScript.py”

My current main project is basically a bunch of individual CLI tools, so I'll do something like "tool-name: Added -k option" or describe the behaviour that changed to fix an issue/bug.

Attached: commits.png (903x363, 47K)

git commit -m "update"

Just reference the Jira card name instead of providing redundant description

It's fine to write "Fixed a bug" and leave it at that if nobody complained about it specifically (and you found it by yourself).

>not having a gitlab hook which rejects pushes if they don't begin with an issue/feature/story number which is open and assigned to you

>Fixing bugs for free

Hahaha programmers are worthless cucks

>fixed the bug
>actually adding backdoors
Anyone else does this?

>"going to sleep now"

fix: Add missing edge cases

Fix some shit and moved other because of this and that.

Reference #111.

fixed a bug ;)

god the absolute fucking state of this shit board
how has nobody said the right thing yet
its not even shitposts its just shit advice posts

here let me break it down for you retard (op):
literally google "good git commmit message" and open the first article

most important points:
use imperative

start with a standardized word for most stuff
could be a set of "Add, Fix, Change, Remove, etc." or "feat.:(short for feature), fix:, chng:, etc.
pick what you'll use with whoever you're working on the repo with, it literally doesnt matter as long as it conforms to some standard

this, someome did actually say it right before me

based Dan.

Imperative present tense.

For example: "Add .NET dependencies"

github.com/ejmg/help-why-cant-i-hold-all-these-mutuals/commits/master

kek

this

commit abcd1234
fix bug

commit abcd1235
features

commit abcd1236
fix bugs with features

commit abcd1237
oh whoops I forgot to commit this last month's work

refs #(ticket ID)

(changed file):
- (short description of change)
- (short description of another change)

(new file)
- (short description of its use)

autism

git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project#_commit_guidelines
github.com/torvalds/subsurface-for-dirk/blob/master/README#L92-L120
chris.beams.io/posts/git-commit/
tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
who-t.blogspot.com/2009/12/on-commit-messages.html
github.com/erlang/otp/wiki/writing-good-commit-messages
github.com/spring-projects/spring-framework/blob/30bce7/CONTRIBUTING.md#format-commit-messages
sethrobertson.github.io/GitBestPractices/

What the fuck did you just fucking say about me, you wittwe bitch? I’ww have you knyow I gwaduated top of my cwass in the Nyavy Seaws, and I’ve been invowved in nyumewous secwet waids on Aw-Quaeda, and I have uvw 300 confiwmed kiwws. I am twainyed in gowiwwa wawfawe and I’m the top snyipew in the entiwe US awmed fowces. You awe nyothing to me but just anyothew tawget. I wiww wipe you the fuck out with pwecision the wikes of which has nyevew been seen befowe on this Eawth, mawk my fucking wowds. You think you can get away with saying that shit to me uvw the Intewnyet? Think again, fuckew. As we speak I am contacting my secwet nyetwowk of spies acwoss the USA and youw IP is being twaced wight nyow so you bettew pwepawe fow the stowm, maggot. The stowm that wipes out the pathetic wittwe thing you caww youw wife. You’we fucking dead, kid. I can be anywhewe, anytime, and I can kiww you in uvw seven hundwed ways, and that’s just with my bawe hands. Nyot onwy am I extensivewy twainyed in unyawmed combat, but I have access to the entiwe awsenyaw of the Unyited States Mawinye Cowps and I wiww use it to its fuww extent to wipe youw misewabwe ass off the face of the continyent, you wittwe shit. If onwy you couwd have knyown what unhowy wetwibution youw wittwe “cwevew” comment was about to bwing down upon you, maybe you wouwd have hewd youw fucking tongue. But you couwdn’t, you didn’t, and nyow you’we paying the pwice, you goddamn idiot. I wiww shit fuwy aww uvw you and you wiww dwown in it. You’we fucking dead, kiddo.

>not being able to clean up technical debt

lmao

*starts twerking*

Avoid frobulating the snaffiscaper (fixes #1337)

Github recognizes and autocloses the issue number.

Start your sentence with "if this gets merged this will..." and then your commit message
It's pretty straightforward
Some examples:
If this gets merged this will...
>Prevent crashing when started as superuser
>Create a new config file
>Add a license to the project
And remember, no past tense in the commit message

Attached: 20091012harrisonstories15.gif (800x1004, 63K)

Like this
reqooes
destroy
pgood
do
pretty
weweboy
wew
hehohe
Merge
wew
wew
company
uhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh
user
righty
fields
uhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh
epws
wew
sugoi
Merge
boatload
wew
those
Merge
wew
give
Merge
cute
Merge
uhhh
>relted_company
Merge
sortboys
ease
add
oops
wewboy
Merge
change
locales
default
add
perfect
wew
fugly
retarded
wew
bromit
Merge
uhhh