[HN Gopher] Comment via GitHub Pull Request
___________________________________________________________________
Comment via GitHub Pull Request
Author : ja3k
Score : 13 points
Date : 2022-01-08 09:29 UTC (1 days ago)
(HTM) web link (ja3k.com)
(TXT) w3m dump (ja3k.com)
| neitherboosh wrote:
| I like projects like this; totally unnecessary, but fun in a kind
| of absurd way.
|
| I tried to post a comment but I didn't really want to fork your
| repo, is there no other way of doing it thru github's api?
| john-doe wrote:
| I wouldn't say unnecessary; most available comment systems are
| either a Discuss-style firehose of tracking scripts, or a pain
| to maintain when self-hosted.
| ja3k wrote:
| Thanks! Yeah it was fun to do. Once I had the idea I felt
| compelled to implement it.
|
| It is a little wasteful to fork the whole repo to make a
| comment. But it seems unavoidable with this design.
| Operyl wrote:
| Forks don't actually create a copy of the git objects, so
| effectively it's just a row in the database.
| brnt wrote:
| Then how come Github shows you the photocopying page,
| sometimes for quite a while? It takes long enough to
| convince me it does more than set a pointer.
| Operyl wrote:
| It's not "just a database row," I oversimplified a bit
| too much perhaps, but it pretty much is very very little
| in the way of data. Since the following blog post, more
| stuff has been added to Git (2018, iirc):
| https://gitlab.com/gitlab-
| org/gitaly/blob/master/doc/delta_i...
| https://gitlab.com/gitlab-org/gitaly/-/issues/1519
|
| https://github.blog/2015-09-22-counting-objects/
|
| > Very early on we figured out that actually forking
| people's repositories was not sustainable. For instance,
| there are almost 11,000 forks of Rails hosted on GitHub:
| if each one of them were its own copy of the repository,
| that would imply an incredible amount of redundant disk
| space, requiring several times more fileservers than the
| ones we have in our infrastructure.
| zauguin wrote:
| I don't know, but since GitHub allows you to show commits
| from any fork with a URL referencing another fork, GitHub
| seems to use a common object store for all forks.
|
| Maybe setting up the separate issue tracker and Pull
| Requests takes some time?
| NoahKAndrews wrote:
| The commit has to be in someone's repo, and GitHub can't
| reasonably allow you to push to a branch on the original repo,
| so you have to make a fork.
| [deleted]
| Operyl wrote:
| This almost feels like it might be a bit cleaner opening an
| "Issue" per blog post/article post, automated via GH:Actions.
| ja3k wrote:
| I posted it to /r/github and someone let me know such a thing
| already exists: https://utteranc.es/ A little cleaner than what
| I've done here.
| john-doe wrote:
| And its clone https://giscus.app/ using Github Discussions
| instead.
___________________________________________________________________
(page generated 2022-01-09 23:01 UTC)