They're a local feature sure. But you already have a list of local commits, just open the .git directory.
Can you connect to a vanilla git server and enumerate every single hash?
> Maybe they should include additional clause about forks there.
It would help but they need much more than a clause about forks.
Ideally they would purge that extra data when making something public.
If you have ssh access yes, but I don't think you can do this with just git (and of course github doesn't provide ssh access to the git repo servers)
The public distribution of commit hashes via their event log seems really irresponsible on github's part to me.
They're a local feature sure. But you already have a list of local commits, just open the .git directory.
Can you connect to a vanilla git server and enumerate every single hash?
> Maybe they should include additional clause about forks there.
It would help but they need much more than a clause about forks.
Ideally they would purge that extra data when making something public.