I can only hope that they never decide to implement "lolreverts"
February 16, 2015 9:50 PM Subscribe
Sometimes a one-line text-only description of your git commits just isn't enough. For those types of scenarios there is software called "lolcommits" that is available for Windows, Mac, and Linux that, when enabled, takes a photo with your webcam every time you commit your code via git. Now you can really let your co-workers know how you feel about having to fix their whitespace issues all the time with just a simple facial expression. After the photo is taken, the git message is overlayed on top of the image is a style reminiscent of lolcats. The resulting image files are then stored locally in your home directory.
Check out some of the sample photos of real people committing real code
Check out some of the sample photos of real people committing real code
"fixes typ" is a classic commit message.
My best so far, is when we added a geolocation API to a project. My commit message was "Yo, man, where you at?". My tech lead had a build server set up that would send him an IM with the commit message whenever a new version was pushed to Master and hit the CI server. He was very confused for a few minutes, thinking maybe Jenkins wanted to hang out or something.
posted by idiopath at 10:10 PM on February 16, 2015 [6 favorites]
My best so far, is when we added a geolocation API to a project. My commit message was "Yo, man, where you at?". My tech lead had a build server set up that would send him an IM with the commit message whenever a new version was pushed to Master and hit the CI server. He was very confused for a few minutes, thinking maybe Jenkins wanted to hang out or something.
posted by idiopath at 10:10 PM on February 16, 2015 [6 favorites]
Follow-up project: lolmergeconflictresolve, which is just a picture of a boot stomping on a developer's face forever.
posted by Itaxpica at 10:30 PM on February 16, 2015 [10 favorites]
posted by Itaxpica at 10:30 PM on February 16, 2015 [10 favorites]
True hell is being stuck in SVN 1.4. I can't believe we can't use git.
posted by five fresh fish at 11:25 PM on February 16, 2015
posted by five fresh fish at 11:25 PM on February 16, 2015
SVN - the version control system that's great at branching, as long as you never ever want to merge that branch back in. Very glad I'm now living in Mercurial land.
posted by kersplunk at 2:29 AM on February 17, 2015 [1 favorite]
posted by kersplunk at 2:29 AM on February 17, 2015 [1 favorite]
Cute. I do all my work in vbox VMs and maybe I could get the local camera working from the host through the VM but I probably won't bother.
posted by octothorpe at 4:27 AM on February 17, 2015 [1 favorite]
posted by octothorpe at 4:27 AM on February 17, 2015 [1 favorite]
Shoulda had this when someone decided to push from their 2 day stale local repo.
(There needs to be a talk that goes "That f flag? Don't use it.")
posted by PMdixon at 4:52 AM on February 17, 2015
(There needs to be a talk that goes "That f flag? Don't use it.")
posted by PMdixon at 4:52 AM on February 17, 2015
At least they fixed Git so it no longer pushes all branches by default when you "git push -f". Been there, done that!
If only there was a webcam around to record my reaction when I realized what I'd done.
posted by neckro23 at 5:08 AM on February 17, 2015
If only there was a webcam around to record my reaction when I realized what I'd done.
posted by neckro23 at 5:08 AM on February 17, 2015
Yeah, never use the -f. And rebase early and often.
posted by octothorpe at 5:25 AM on February 17, 2015
posted by octothorpe at 5:25 AM on February 17, 2015
I can't wait for the first rage quit commit.
oh, and not nearly enough " I can't believe git/hg/whatever makes me have to do this shit over and over" looks.
I've been doing this so long I just see that git sucks less in some specific ways.
posted by clvrmnky at 5:47 AM on February 17, 2015
oh, and not nearly enough " I can't believe git/hg/whatever makes me have to do this shit over and over" looks.
I've been doing this so long I just see that git sucks less in some specific ways.
posted by clvrmnky at 5:47 AM on February 17, 2015
I like the "fingers crossed!" snap of someone adding a feature.
Although the misspellings in commits really makes me fear for the code itself. Why yes I did use vi right on a dev server for 10 years. IDE? Pssh.
posted by travertina at 6:39 AM on February 17, 2015
Although the misspellings in commits really makes me fear for the code itself. Why yes I did use vi right on a dev server for 10 years. IDE? Pssh.
posted by travertina at 6:39 AM on February 17, 2015
> True hell is being stuck in SVN 1.4. I can't believe we can't use git.
Of course you can.
The pictures are kind of neat, a reminder that there really are people behind the code. It's one reason why I like to follow planet fedora and planet debian. It gives you a more human connection to what is going on.
posted by Poldo at 6:44 AM on February 17, 2015
Of course you can.
The pictures are kind of neat, a reminder that there really are people behind the code. It's one reason why I like to follow planet fedora and planet debian. It gives you a more human connection to what is going on.
posted by Poldo at 6:44 AM on February 17, 2015
He was very confused for a few minutes, thinking maybe Jenkins wanted to hang out or something.
Commit ad878da32: Hey, baby, wanna parse code with me?
posted by eriko at 6:52 AM on February 17, 2015
Commit ad878da32: Hey, baby, wanna parse code with me?
posted by eriko at 6:52 AM on February 17, 2015
Of course you can.
Depends a lot on the rest of your environment. git-svn is unsupported by a lot of IDEs (e.g. PyCharm, PhpStorm).
posted by jedicus at 7:04 AM on February 17, 2015
Depends a lot on the rest of your environment. git-svn is unsupported by a lot of IDEs (e.g. PyCharm, PhpStorm).
posted by jedicus at 7:04 AM on February 17, 2015
Yeah, never use the -f. And rebase early and often.
alias yolo='git commit -am "DEAL WITH IT" && git push -f origin master'
One real issue with git is that it's built to make things easy for the maintainer, not the contributor. This should surprise exactly nobody who know who wrote it and why.
posted by eriko at 7:05 AM on February 17, 2015 [6 favorites]
alias yolo='git commit -am "DEAL WITH IT" && git push -f origin master'
One real issue with git is that it's built to make things easy for the maintainer, not the contributor. This should surprise exactly nobody who know who wrote it and why.
posted by eriko at 7:05 AM on February 17, 2015 [6 favorites]
Not if I want to keep the contract, Poldo.
posted by five fresh fish at 7:30 AM on February 17, 2015
posted by five fresh fish at 7:30 AM on February 17, 2015
lol-git-reflog (look of terror)
posted by double block and bleed at 8:56 AM on February 17, 2015 [1 favorite]
posted by double block and bleed at 8:56 AM on February 17, 2015 [1 favorite]
One real issue with git is that it's built to make things easy for the maintainer, not the contributor.
Huh. I would've called that a feature, not a bug.
posted by twirlip at 9:27 AM on February 17, 2015 [1 favorite]
Huh. I would've called that a feature, not a bug.
posted by twirlip at 9:27 AM on February 17, 2015 [1 favorite]
>> Yeah, never use the -f. And rebase early and often.
> alias yolo='git commit -am "DEAL WITH IT" && git push -f origin master'
Are you familiar with git koans?
(I smirked. Then I sobbed.)
A Python programmer handed her ~/.gitconfig to Master Git. Among the many lines were the following:
[alias]
; Explicit is better than implicit. If we want to merge
; we should do so ourselves.
pull = pull --ff-only
Master Git nodded. “git pull origin master,” said the programmer.
Master Git pulled down the latest changes on master and automatically merged them with the programmer’s changes.
“But Master Git, did I not say to only fast-forward in my configuration?!” she cried.
Master Git looked at her, nodded, and said nothing.
“Then why did you not warn me of a problem with my configuration?” she asked.
Master Git replied: “there was no problem.”
Months later the programmer was reading git --help config for a different reason and found enlightenment.
posted by RedOrGreen at 10:00 AM on February 17, 2015 [2 favorites]
> alias yolo='git commit -am "DEAL WITH IT" && git push -f origin master'
Are you familiar with git koans?
(I smirked. Then I sobbed.)
A Python programmer handed her ~/.gitconfig to Master Git. Among the many lines were the following:
[alias]
; Explicit is better than implicit. If we want to merge
; we should do so ourselves.
pull = pull --ff-only
Master Git nodded. “git pull origin master,” said the programmer.
Master Git pulled down the latest changes on master and automatically merged them with the programmer’s changes.
“But Master Git, did I not say to only fast-forward in my configuration?!” she cried.
Master Git looked at her, nodded, and said nothing.
“Then why did you not warn me of a problem with my configuration?” she asked.
Master Git replied: “there was no problem.”
Months later the programmer was reading git --help config for a different reason and found enlightenment.
posted by RedOrGreen at 10:00 AM on February 17, 2015 [2 favorites]
Huh. I would've called that a feature, not a bug.
It is -- if you're the maintainer.
posted by eriko at 12:42 PM on February 17, 2015
It is -- if you're the maintainer.
posted by eriko at 12:42 PM on February 17, 2015
Ha! I tried this out a few years ago. You should be forewarned that the results may not be super flattering.
posted by creade at 2:42 PM on February 17, 2015
posted by creade at 2:42 PM on February 17, 2015
Yeah, as someone who generally hates seeing pictures of himself, I'll give it a pass, but am happy to laugh at the pictures of other people using it.
posted by idiopath at 5:27 PM on February 17, 2015
posted by idiopath at 5:27 PM on February 17, 2015
« Older American Tintype | @Pats28Hawks24 Newer »
This thread has been archived and is closed to new comments
posted by mathowie at 9:55 PM on February 16, 2015 [3 favorites]