Perhaps GitHub should only do this for signed commits or commits to the author's own repository or something.
GitHub also allows you to add anyone to a project without their consent (or has this changed?). This reminds me of the Facebook prank where someone added Mark Zuckerberg to a fake(?) pro-paedophile group.
It should be trivial for them to allow you to paste your pgp public key as you would your ssh public key, then place a nice little "verified" check mark next to commits that can be validated as having been signed with one of your associated private keys.
on a slow connection, this allows you to work on or inspect repos that are too large to git clone (one of the few major complaints i have with git itself)
I really wonder what they do. I have some complicated feelings about them, also, that has to do with them becoming the central hub for open source.
Like, if the product itself were open source, it might be more obvious what they are working on. But I can't demand that kind of transparency... It would just be interesting to know.
With almost 500 employees, what happens? I've never even worked at such a large company myself.
Should GitHub users have some say in what the company builds? I mean, we're promoting them like hell, and the social network is a huge part of their value.
I often wonder what well-funded large product companies do with all their manpower. Feature development doesn't seem to scale. Nor innovative design. GitHub's mobile layout is pretty crippled. I dunno. Just curious.
Of course, this has always been possible with git.
I reported this issue a long time ago to their security team, and got a really condescending "we're a collaborative community, it's not a problem, you obviously don't understand" type of response. Pretty frustrating.
Or consider the common case where the public repository on Github is just a mirror of an official repository somewhere else -- then commits from a bunch of people would all be pushed by whoever is responsible for keeping the repos in sync.
But maybe Github could just add some kind of a "pushed by" label that identifies the Github user who pushed the commit?
Even worse: rebasing (what rewriting an old commit actually does) changes all SHA hashes of the following commits, thus breaking existing PGP signatures on the commits. There should be two signatures... one for the patch+comment, one for the history.
It shows up as "Bob committed with Alice".
I've only noticed it showing up for cherry-picks, I'm unsure if that's the only place it's used.
All one has to do to make it go away is change the committer field on the git, this isn't security added by GitHub.
It already has the keys set up and such.
Oops. Thanks for the correction.