I love that this enforces a social practice a lot of teams use already, and I'm pushing to add it to my own team's workflow (both internal and for open source contributions).
Edit: another tool in the same vein people might be interested in is Facebook's mention-bot [3], which analyzes PR diffs and @-mentions people it thinks would be good reviewers based on git blame of lines touched.
I cannot find a way to "undo LGTM" if I was to quick to give approval. Working at a company where I have to LGTM commits literally every day, believe me that it is necessary every now and then.
it would definitely be trivial to add the ability to rescind an approval with a -1, for example. Unfortunately I'm a bit bogged down with my other OSS projects at this time, but I would be happy to accept a PR. In fact, this is the function you would want to update https://github.com/lgtmco/lgtm/blob/master/web/hook.go#L100
http://homu.io goes a bit further (it actually triggers CI builds of the merge results to check they are okay), but it seems it is currently unmaintained.
BTW, I would gladly pay money for this! Even more in combination with features from Facebook's mention-bot/Rust's highfive.
> http://homu.io goes a bit further (it actually triggers CI builds of the merge results to check they are okay), but it seems it is currently unmaintained.
barosl apparently hasn't had the time to work on it, and homu-as-a-service has apparently stopped working some time ago. After discussing it with barosl Rust has apparently moved to the Servo fork of it: https://github.com/servo/homu
No bors/homu as a service at this point though, sadly.
There are two pull requests we are working to merge that might be of interest. First is the ability to auto-merge once all approvals are received. Second is the ability to auto-tag a release once all approvals are received.
Regarding CI, this generally works in conjunction with a CI server. You can specify, via github protected branches configuration, that both LGTM and your CI checks must pass before merging.
Is this type of functionality planned for an official GitHub feature? Gitlab and Bitbucket both incorporate some type of similar functionality already...
Not talking about the project, but is the term 'LGTM' (looks good to me) used often in tech? I've heard it from Googlers but otherwise haven't really seen the term in tech.
Same here we are using it for most of our commits. When someone is done with their changes, they issue a PR which is reviewed by one or two team members before being rejected or merged by saying LGTM.
Same here we are using it for most of our commits. When someone is done with their changes, they issue a PR which is reviewed by one or two team members before being rejected or merged by saying LGTM.
Depends on the company, but at SendGrid it's standard practice in the code review stage to wait for Looks Good To Me - no more changes needed - before merging.
Much like this submission, our continuous integration system (opsbot) doesn't let you continue through the workflow until you have a "LGTM" comment from another developer. This prevents lone-developer cowboy merges with no review. :)
I had assumed it was very common. The small start up I worked at used it. One of the developers was really fond of using this plugin for all his LGTM comments
Since we're talking about GitHub pull requests, my favorite tool for this is https://reviewable.io/. It fixes basically everything about GitHub pull requests.
And of relevance to the original article, in Reviewable you can customize your review completion condition with a snippet of code it will run on your behalf and post the result as a GitHub commit status, so you can have basically any approval system you want. One of the examples is a simple LGTM-based system like in OP.
LGTM doesn't currently work with GitHub reactions mostly because the API [1] wasn't available back in November when the project was created. I do personally like comments because they are a bit more visible than reactions, which require you to hover over to see more details.
Now that the reactions API is available it is certainly possible to enable this sort of functionality. I openly encourage people to fork the project and hack into something that works for their team.
61 comments
[ 0.28 ms ] story [ 127 ms ] threadWorks well for the team I'm on.
1: https://github.com/airbnb/enzyme/pull/449
2: https://github.com/airbnb/enzyme/pull/459
I love that this enforces a social practice a lot of teams use already, and I'm pushing to add it to my own team's workflow (both internal and for open source contributions).
Edit: another tool in the same vein people might be interested in is Facebook's mention-bot [3], which analyzes PR diffs and @-mentions people it thinks would be good reviewers based on git blame of lines touched.
3: https://github.com/facebook/mention-bot
BTW, I would gladly pay money for this! Even more in combination with features from Facebook's mention-bot/Rust's highfive.
barosl apparently hasn't had the time to work on it, and homu-as-a-service has apparently stopped working some time ago. After discussing it with barosl Rust has apparently moved to the Servo fork of it: https://github.com/servo/homu
No bors/homu as a service at this point though, sadly.
https://github.com/rust-community/team/issues/41
https://github.com/barosl/homu/issues/122
https://github.com/barosl/homu/issues/151
Regarding PR queuing do you mean https://gitlab.com/gitlab-org/gitlab-ce/issues/4176 ?
Regarding CI, this generally works in conjunction with a CI server. You can specify, via github protected branches configuration, that both LGTM and your CI checks must pass before merging.
I had a coworker who didn't know what it meant, and somehow assumed it was "Let's Get That Money". So now I think of that every time :)
Much like this submission, our continuous integration system (opsbot) doesn't let you continue through the workflow until you have a "LGTM" comment from another developer. This prevents lone-developer cowboy merges with no review. :)
https://chrome.google.com/webstore/detail/lgtm/oeacdmeoegfag...
"Looks Good to Me"
or
"Let's Get this Moving"?
:-)
(Disclaimer: I run reviewable.io.)
Now that the reactions API is available it is certainly possible to enable this sort of functionality. I openly encourage people to fork the project and hack into something that works for their team.
[1] https://developer.github.com/changes/2016-05-12-reactions-ap...
I blogged about that here: http://thepugautomatic.com/2014/02/code-review/
We use a home-grown tool on top of GitHub to review commit-by-commit after the fact: https://github.com/henrik/remit