3 ms·
No, it's a bug in GitHub. It should be a 404, or at least redirect to my fork, where that commit was actually made.
by AndyKelley 8y ago
No, it's a bug in GitHub. It should be a 404, or at least redirect to my fork, where that commit was actually made.
- WorldMaker 8y agoIt is a likely sort of GitHub bug. It's pretty well known that GitHub stores all objects for all forks of a repository in a single git object database and it has added guards to git (some of which have been upstreamed into git itself) to keep it from navigating objects outside of a particular fork. It's a small, easy to miss detail in this screenshot because you are looking for the lack of something, but under the commit title is where GitHub lists the containing branches and tags of the current fork, and in this case that line is entirely missing. (GitHub should maybe have a more explicit negative message in this sort of case: "This commit does not seem to be included in any of this fork's branches or tags.")