So any thoughts on this company, Repography? Their dashboards look really cool, but the only way to give them a go with my own repositories is to authorize their Github app to "Act on my behalf", whatever that means, or to curl some unknown code and pipe that into bash locally on my machine. Neither option is one I'm particularly fond of trying, without additional assurances that this is a legit org.
I don't know. I just feel like they could have spent a bit more time convincing me it's safe to do that authorization thing. Likewise, I could have downloaded their script and audited it before running - I just don't have the time to do that right now.
The Go language's first commit (1972)
11–20 of 50 posts
Re: The Go language's first commit (1972)
#12So any thoughts on this company, Repography? Their dashboards look really cool, but the only way to give them a go with my own repositories is to authorize their Github app to "Act on my behalf", whatever that means, or to curl some unknown code and pipe that into bash locally on my machine. Neither option is one I'm particularly fond of trying, without additional assurances that this is a legit org. I don't know. I…
Hi, I'm Arpad, one half of Repography.
There's an entry in our FAQ [1] about this. We only use OAuth to identify your GitHub account and then the GitHub app installation has much better defined permissions.
I'd love to be able to restrict the OAuth scope even further but GitHub doesn't let us. I've heard this concern a couple of times now so I'll have another look. I can hopefully at least improve how it's presented and communicated so it's more reassuring!
Re: The Go language's first commit (1972)
#13How would that even work if git was released in 2005? Am I missing something?
Obviously, code that old couldn't have been originally committed to git. But it is quite common to have old repositories migrated to git and one would expect the original time stamps been maintained after the migration.
Re: The Go language's first commit (1972)
#14See also https://news.ycombinator.com/item?id=12371029 (from 2016)
Re: The Go language's first commit (1972)
#15So any thoughts on this company, Repography? Their dashboards look really cool, but the only way to give them a go with my own repositories is to authorize their Github app to "Act on my behalf", whatever that means, or to curl some unknown code and pipe that into bash locally on my machine. Neither option is one I'm particularly fond of trying, without additional assurances that this is a legit org. I don't know. I…
Hi, I'm Arpad, one half of Repography. There's an entry in our FAQ [1] about this. We only use OAuth to identify your GitHub account and then the GitHub app installation has much better defined permissions. I'd love to be able to restrict the OAuth scope even further but GitHub doesn't let us. I've heard this concern a couple of times now so I'll have another look. I can hopefully at least improve how it's presented…
The back button is broken on your website.
Re: The Go language's first commit (1972)
#16This was done as a joke. Go was released. Someone else claimed he owns the name "Go" for a programming language. As a proof his github "go language" creation and commit date was shown. This wasn't fake, was real. Google surely won't give up for this reason. Few days later google extended their go commit to 1972. Preceding that author's date by a long shot. Guess you can find the news coverage from that time if you se…
The "Go!" language, right?
I mean the language was first IIRC.
Re: The Go language's first commit (1972)
#17How would that even work if git was released in 2005? Am I missing something?
Obviously, code that old couldn't have been originally committed to git. But it is quite common to have old repositories migrated to git and one would expect the original time stamps been maintained after the migration.
In 1972 the web was still only available in black and white and a typical consumer laptop was the size of a steamer trunk.
Re: The Go language's first commit (1972)
#18Where are the cool free projects? This repography is yet another product that wants my money.
Re: The Go language's first commit (1972)
#19Earlier quoted context omitted.
Obviously, code that old couldn't have been originally committed to git. But it is quite common to have old repositories migrated to git and one would expect the original time stamps been maintained after the migration.
In 1972 the web was still only available in black and white and a typical consumer laptop was the size of a steamer trunk.
Sorry, what do you want to say with that? I was talking in general, why Git repositories might contain commits which precede the creation of Git by a large amount. And I am sure, while no one committed the code in 1972 to any kind of repository, that the code snipped with its date is genuine. At that time Kernighan was working with other legends off the Unix world on Unix and the C language.
Re: The Go language's first commit (1972)
#20How would that even work if git was released in 2005? Am I missing something?
I have git repos with commits from before 2005 in projects converted from cvs, to subversion to git.