[ittan]

It is because the features on github.com directly correlate to a git feature.

[casion]

Ah yes, pull requests and adjacent functionality is my favorite part of git.

[jolux]

There is, in fact, an analogous Git feature: https://git-scm.com/docs/git-request-pull

[sigstoat]

so where’s the one that correlates to git log —graph ?

[tim--]

Click 'commits' on any repo and you will see the graph.

[ori_b]

Where does it show the branches and merges?

[FPGAhacker]

It’s weird if GitHub doesn’t have that. Gitlab does. https://gitlab.com/gitlab-org/gitlab-runner/-/network/main

[jcranmer]

That would be the network view.

[sigstoat]

that only shows you inter-repository activity, not the branches within a repo.

that would be worthless for most people, and for the sqlite authors, who'd surely have a million people pressing the 'fork' button.

it also isn't what anyone in the thread, or post, were asking for.

[sigstoat]

all i've ever seen is something which displays a single branch, and does not contain the graph structure information present in git log --graph.

perhaps you'd be so kind as to provide a link to a page on github which demonstrates the same graph structure?

[leephillips]

I’ve never found that either. I try to limit my interactions with GitHub to copying the URL to clone and doing pull requests. GitHub has the same relationship to Git as OverLeaf has to LaTeX: a layer of excrement smeared over and defacing a beautiful program. The saddest thing is that much of the current generation of programmers think that GitHub is Git.

[rezonant]

Curious: What git feature does Network mirror then?

[lelandfe]

Under the hood, “forks” are really just fancy branches. So realistically that would also be git log

[auxym]

git log?

[rezonant]

Hmm, GitHub Network is much more than log. I think "GitHub Commits" page mirrors git log.

[Ajedi32]

Network is more like `git log --graph --decorate --oneline`. Still git log, just in a slightly different format.

[alex_smart]

> Network is more like `git log --graph --decorate --oneline`

... across all forks, which makes the UI much more cluttered than it needs to be. What if you are only interested in commits in your own repo?

Github really does seem to lack a clean equivalent of `git log --graph`.

[rezonant]

`git log --graph --decorate --oneline` is specific to a branch of a repository. Github Network shows the relationship between forks. It is similar but really the question answered by it is "what and where is the work being done" and "what is the relationship between work being done and this repository I'm looking at". It sucks that Network is buried, I think it should be much more accessible.

Eg https://github.com/sindresorhus/delay/network tells me that this work is being maintained actively, but most forks are not merging back. Another one might tell me work on the main fork is stalled, and many users are now doing PRs against a fork of the original.

[est31]

Maybe git log --graph --decorate --oneline --all then? Github implements forks as just fancy branches in the same repo. Adding the all param includes all branches.