News for hackers. Stuff that matters.
Re:Why SQLite does not use Git (2018) by rezonant on Friday November 05, 2021 @08:56PM (#29126432)
Hmm, GitHub Network is much more than log. I think "GitHub Commits" page mirrors git log.
Re:Why SQLite does not use Git (2018) by Ajedi32 on Friday November 05, 2021 @09:25PM (#29126644)
Network is more like `git log --graph --decorate --oneline`. Still git log, just in a slightly different format.
Re:Why SQLite does not use Git (2018) by alex_smart on Friday November 05, 2021 @09:52PM (#29126819)
> 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`.

Re:Why SQLite does not use Git (2018) by rezonant on Friday November 05, 2021 @09:50PM (#29126808)
`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.

Re:Why SQLite does not use Git (2018) by est31 on Friday November 05, 2021 @11:10PM (#29127164)
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.