On Thu, Dec 15, 2011 at 6:04 PM, Robert Clipsham <rob...@octarineparrot.com> wrote: > I just read this pretty interesting article on the Google Engineering Tools > website, thought it might interest some people here: > > http://google-engtools.blogspot.com/2011/12/bug-prediction-at-google.html > > ( http://goo.gl/2O6YT <= a short link in case the above one gets wrapped) > > It basically describes a new process in place at Google whereby each file > within a project is assigned a rating saying how likely the given file is to > have a bug in it compared to everything else. This can be used by code > reviewers so they can take extra care when reviewing certain changes. > > I really think github needs built in review tools (more advanced than just > pull requests) to allow things like the auto-tester to be run, or algorithms > like this to be used for manual review and so on. >
Well, Github does have an API to allow that sort of thing to happen. In theory, a bot could examine a pull request, merge it and run tests, and post back the results.
