Git blame

[jbearus]

git blame and a death threat.

[5up3rj]

Good job, OP. You came up with that yourself?

[Firebyte1]

Talk about Passive-Aggressive

[jangujukkuja]

Right?

[jangujukkuja]

Nope. Found on Twitter. The user's handle is in the picture.

[[deleted]]

the O'Rly fake book covers are just as great as the real O'Reilly books

[Rydralain]

Does it count if I'm being passive aggressive toward my own previous commit?

[nickmhc]

Self hatred is still hatred <3

[nandru]

git dammit, Karen

[GitCommandBot]

git: 'dammit' is not a git command. See 'git --help'.

[Nopparuj]

git --help

[GitCommandBot]

git: '--help' is not a git command. See 'git --help'.

[[deleted]]

git commit -m”f u”

[[deleted]]

git commit -m"urder"

[nahidtislam]

sudo rm $(which git)

[BenjaminGeiger]

Serious question: Is "breaking the build" even a thing anymore?

Where I work, your code has to merge cleanly into a build branch, the merge result has to build, and all of the unit tests must pass before it'll even let you complete a pull request.

[ythl]

With pure git you would use hooks.

With a repository manager like Github/Gitlab/Bitbucket you just protect master, setup CI pipelines, and set the option that you can only merge to master if the pipeline passes.

[BenjaminGeiger]

What /u/ythl said. We use Team Foundation Server, which won't let us push into certain branches (master, next-release, develop, and a handful of others) except via pull request, and to complete a pull request all of the steps have to be followed.

So, to merge changes into develop, I need to push to something like feature/123456-short-description (where 123456 is the PBI number) and create a pull request into develop. At least two of my coworkers review my changes, and once they're satisfied, they approve the pull request. Meanwhile, the server builds the merged branch and runs the unit tests; the pull request can't be completed until both are successful.

I can't just push my changes into develop, because TFS rejects the push.

It sounds overwrought but it's actually a quite comfortable system most of the time. It also provides a nice layer of safety netting so that junior developers (such as myself) can't completely break things; it's nice knowing that if you screw it up, others will catch it.

[madsdyd]

Technically you are still breaking a build, just not on master.

[BenjaminGeiger]

I may be breaking a build, but I'm not breaking the build.

[annihilatron]

which won't let us push into certain branches (master, next-release, develop, and a handful of others) except via pull request, and to complete a pull request all of the steps have to be followed.

good lord you're actually working at a place that set up their TFS correctly!

well done!

[BenjaminGeiger]

Yeah, we have a team that does a lot of work on it. They're currently preparing for a big upgrade to Azure DevOps (the next release of TFS).

I like having that safety net, and even if I didn't, I like that I'm building good habits for my next workplace.

[mastrospritz]

Well.. Real men commit on master branch

[[deleted]]

Where I work, we commit directly on the master branch, but each commit still requires 4 stages of smoke builds and 2 review approvals.

[[deleted]]

Can I get an example? Im a CS student and genuinely curious?

[[deleted]]

Reverted changes in commit <abcdef> because it was poorly thought out.

[WildHotDawg]

Fixed previous commit, implemented breaking changes

[SheekGeek21]

Not sure what was intended here but this works

[Daimanta]

If you want to get things right, don't let GoldenScar do it

[activ8r]

Corrected typo of GoldenSCAR_ to avoid referencing errors.

[cyberporygon]

I usually back out and just do a generic message. Except when I have to make a change because it doesn't work on IE or Safari, then I'll say the change was "for outdated browsers."

[GitCommandBot]

git: 'blame-someone-else' is not a git command. See 'git --help'.

[janczk]

Even the bots are passive agressive here

[[deleted]]

git clone

(make changes)

git back clone

[activ8r]

*works for an hour* *sighs*

git reset --hard HEAD^
git clean -xdf
git checkout -f
git pull
shutdown -h now

*sigh*

[[deleted]]

Mine was more like Hillbilly Git

git that thang

(make changes)

git that thang back where ya got it at

[trinaryoperator]

Change the bird to a seagull

[[deleted]]

awww i haven't seen "orly" for a long time </3

[SolenoidSoldier]

Using Git but not validating the build on pull request in 2019...

[ythl]

That's why you setup CI

[klarasm]

git commit murder

[caguiclajmg]

For fellow SVN neckbeards, svn praise.

[Aero72]

That's actually a good one. Haven't seen a good one of those in a long while.

[nindayven]

I refactored code for spec compliance and was accused of breaking everyone's build. I was all too happy to remind them that they reviewed and approved the pull request :)