How to take credit for someone else's work on GitHub

• git-upstage

  1 164 10.0 Shell

  Take credit for someone else's work; or, a typo gone too far.

I remember this earlier subthread where someone was criticizing GitHub for allowing this (even using Torvald as someone to impersonate!), and others offered some defenses (which were IMHO dubious):

https://news.ycombinator.com/item?id=21025378

Also, semi-related, obligatory mention of my joke utility for stealing credit for someone else's work:

https://github.com/silasx/git-upstage

Finally, I thought this phrasing was funny, like commits have a non-substantively transferable ownership, like an NFT (though FYI it's quoting an older discussion of the same problem):

>Someone wrote about the whole situation on Medium in November 2021: "The 1st commit of git/git no longer belongs to Linus Torvalds".

• emails

  19 - -

GitHub bases the association of commits to user accounts on the list of e-mail addresses configured in the user’s profile: https://github.com/settings/emails

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• litestream

  165 9,997 7.5 Go

  Streaming replication for SQLite.

I had this happen on a small PR I submitted within the past year. I didn’t think anything of it at the time, but your comment led me to glancing through the past PRs and it’s comical how many are closed with a “thanks, I’ve committed an equivalent patch” comment.

One the one hand, it’s his repo and he’s free to do whatever he wants. I actually admire how ruthless the maintainer is on closing issues, must be great for staving off OSS burnout.

On the other hand, I don’t love how antagonistic it is to outside contributors. Litestream[0] is an example of open source-closed contributions, but at least it’s upfront about that in the README. (And the policy has actually changed to open for bug fixes.) I would open an issue/PR on Huey suggesting adding a similar disclaimer, but it’d probably be closed, ha.

[0] https://github.com/benbjohnson/litestream#contribution-polic...

• git-blame-someone-else

  108 10,632 0.0 Shell

  Blame someone else for your bad code.

Now you're thinking like the author of git-blame-someone-else: https://github.com/jayphelps/git-blame-someone-else

• forceatlas2

  2 271 0.0 Python

  Fastest Gephi's ForceAtlas2 graph layout algorithm implemented for Python and NetworkX

Or you can just do this: https://github.com/bhargavchippada/forceatlas2/commit/7438e2...

• forceatlas2-python

  1 5 10.0 Python

  A port of Gephi's ForceAtlas2 graph layout algorithm to Python and NetworkX. See the bzr page for updates.

This appears to be the repo that the copyright originated from

https://github.com/mwshinn/forceatlas2-python

bhargavchippa also contributed to this repo, so this doesn't seem like one of those random "fork and lie" sort of thing. Without the necessary context, we can't assume much. It could well be that mwshinn was in the wrong or there was an "okay" from mwshinn for bhargavchippa to make those changes.

Suggest a related project