Search commit messages

#1

Post by moby » Tue, Jan 03, 2017, 11:29 PM UTC

Re: Search commit messages

#2

Post by tomschlick » Tue, Jan 03, 2017, 11:42 PM UTC

Should be an interesting research tool to see how often we use shitty commit messages when trying to get something fixed...

https://github.com/search?utf8=%E2%9C%93&q=fix&type=Commits&...

Re: Search commit messages

#3

Post by hosainnet » Tue, Jan 03, 2017, 11:59 PM UTC

tomschlick wrote: post #2

Should be an interesting research tool to see how often we use shitty commit messages when trying to get something fixed... https://github.com/search?utf8=%E2%9C%93&q=fix&type=Commits&...

"Actually fixed" https://github.com/search?utf8=%E2%9C%93&q=%22actually+fixed...

Re: Search commit messages

#4

Post by cmrx64 » Wed, Jan 04, 2017, 12:33 AM UTC

hosainnet wrote: post #3

tomschlick wrote: post #2

Should be an interesting research tool to see how often we use shitty commit messages when trying to get something fixed... https://github.com/search?utf8=%E2%9C%93&q=fix&type=Commits&...

"Actually fixed" https://github.com/search?utf8=%E2%9C%93&q=%22actually+fixed...

I'm definitely guilty of this one. My big mistake is I always think "oh this will be an easy fix" when configuring a CI system, and then it doesn't work, and I don't split into a new branch then and there.

Re: Search commit messages

#5

Post by cmrx64 » Wed, Jan 04, 2017, 12:34 AM UTC

I'm curious how long it took to build their search index, and how they do it/what technologies/algorithms they are using. That's a lot of data!

Re: Search commit messages

#6

Post by relics443 » Wed, Jan 04, 2017, 1:02 AM UTC

Google put all GitHub data in BigQuery a while back [1]. What took them so long?

[1] https://cloud.google.com/bigquery/public-data/github

Re: Search commit messages

#7

Post by lemming » Wed, Jan 04, 2017, 1:05 AM UTC

hosainnet wrote: post #3

tomschlick wrote: post #2

Should be an interesting research tool to see how often we use shitty commit messages when trying to get something fixed... https://github.com/search?utf8=%E2%9C%93&q=fix&type=Commits&...

"Actually fixed" https://github.com/search?utf8=%E2%9C%93&q=%22actually+fixed...

"fixed this time": https://github.com/search?utf8=%E2%9C%93&q=%22fixed+this+tim...

Just the first page is pretty funny.

Re: Search commit messages

#8

Post by WillAbides » Wed, Jan 04, 2017, 1:10 AM UTC

lemming wrote: post #7

hosainnet wrote: post #3

Earlier quoted context omitted.

"Actually fixed" https://github.com/search?utf8=%E2%9C%93&q=%22actually+fixed...

"fixed this time": https://github.com/search?utf8=%E2%9C%93&q=%22fixed+this+tim... Just the first page is pretty funny.

"really really fixed this time for real"

Re: Search commit messages

#9

Post by sdesol » Wed, Jan 04, 2017, 1:18 AM UTC

relics443 wrote: post #6

Google put all GitHub data in BigQuery a while back [1]. What took them so long? [1] https://cloud.google.com/bigquery/public-data/github

Well this is an apple and orange thing. With BigQuery, they deal with data dumps, while GitHub deals with constant streams of new data. However I do agree with the "What took so long?" sediment.

This is something that should have been in place 3 years ago. I guess it's a good that GitLab is lighting the fire under them, as we all benefit. Given the resources they have, it really is puzzling, they couldn't understand what was important for increasing software development productivity.

I'm guessing they heard enough of "what do you mean we can't search for commits?" from potential/existing Enterprise customers, that they realized this was actually important.

Re: Search commit messages

#10

Post by pix64 » Wed, Jan 04, 2017, 5:23 AM UTC

tomschlick wrote: post #2

Should be an interesting research tool to see how often we use shitty commit messages when trying to get something fixed... https://github.com/search?utf8=%E2%9C%93&q=fix&type=Commits&...

These links do not work if you're not logged in.