Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub Is Down?

news.ycombinator.com

Post reply on HN
Print view View original

31–39 of 39 posts

Re: GitHub Is Down?

#31

Post by DoofusOfDeath »

diggan wrote: post #23
rubenbe wrote: post #20

This is the perfect moment to stress that git is decentralized, so you can push/pull directly from you colleagues. The fact that github is down is a only poor excuse for an extended coffee break. ;) (Down from BE)

Unless most of us are stupid enough to use GitHub issues and PRs instead of having that data in the repository itself.

> Unless most of us are stupid enough to use GitHub issues and PRs instead of having that data in the repository itself.

When I looked into this years ago, I couldn't find any good tools for using the repository itself as the data storage layer for bug tracking, PRs, etc. So (at least then) Github was the best option.

Can you recommend any alternatives?

Re: GitHub Is Down?

#32

Post by jakobegger »

diggan wrote: post #23
rubenbe wrote: post #20

This is the perfect moment to stress that git is decentralized, so you can push/pull directly from you colleagues. The fact that github is down is a only poor excuse for an extended coffee break. ;) (Down from BE)

Unless most of us are stupid enough to use GitHub issues and PRs instead of having that data in the repository itself.

I really like that Issues / PR are centralised. The last thing I want is merge conflicts with issue comments... just the thought of that is horrible...

Re: GitHub Is Down?

#33

Post by fxfan »

DoofusOfDeath wrote: post #31
diggan wrote: post #23

Earlier quoted context omitted.

Unless most of us are stupid enough to use GitHub issues and PRs instead of having that data in the repository itself.

> Unless most of us are stupid enough to use GitHub issues and PRs instead of having that data in the repository itself. When I looked into this years ago, I couldn't find any good tools for using the repository itself as the data storage layer for bug tracking, PRs, etc. So (at least then) Github was the best option. Can you recommend any alternatives?

fossil from the creator of SQLite

Re: GitHub Is Down?

#34

Post by stephenr »

pvinis wrote: post #24
diggan wrote: post #23

Earlier quoted context omitted.

Unless most of us are stupid enough to use GitHub issues and PRs instead of having that data in the repository itself.

Is there actually something like that? A way to have issues inside the repo?

BugsEverywhere (https://gitlab.com/bugseverywhere/bugseverywhere) does this, but the project isn't overly active these days.

The nice thing about BE compared to the more recent ones, is that it's VCS agnostic - it's just files in the repo, rather than e.g. using some special metadata feature of git/etc to track the issues.

I've yet to see a web UI for it tough (to expose it to non-technical users).

Re: GitHub Is Down?

#35

Post by diggan »

jakobegger wrote: post #32
diggan wrote: post #23

Earlier quoted context omitted.

Unless most of us are stupid enough to use GitHub issues and PRs instead of having that data in the repository itself.

I really like that Issues / PR are centralised. The last thing I want is merge conflicts with issue comments... just the thought of that is horrible...

I agree, I wouldn't want to have merge conflicts in issues/PRs either, but I don't think just because it's decentralized, means that it would have conflicts. A quick thought would be to have issues/PRs only editable by the author via signing for example. Not allow any edits and just modifications on top of other modifications.

Is there a reason you prefer centralization that is not about conflicts?

Re: GitHub Is Down?

#36

Post by diggan »

DoofusOfDeath wrote: post #31
diggan wrote: post #23

Earlier quoted context omitted.

Unless most of us are stupid enough to use GitHub issues and PRs instead of having that data in the repository itself.

> Unless most of us are stupid enough to use GitHub issues and PRs instead of having that data in the repository itself. When I looked into this years ago, I couldn't find any good tools for using the repository itself as the data storage layer for bug tracking, PRs, etc. So (at least then) Github was the best option. Can you recommend any alternatives?

I put up three links in a different comment here: https://news.ycombinator.com/item?id=19848369

Re: GitHub Is Down?

#37

Post by jakobegger »

diggan wrote: post #35
jakobegger wrote: post #32

Earlier quoted context omitted.

I really like that Issues / PR are centralised. The last thing I want is merge conflicts with issue comments... just the thought of that is horrible...

I agree, I wouldn't want to have merge conflicts in issues/PRs either, but I don't think just because it's decentralized, means that it would have conflicts. A quick thought would be to have issues/PRs only editable by the author via signing for example. Not allow any edits and just modifications on top of other modifications. Is there a reason you prefer centralization that is not about conflicts?

Knowing that everyone sees what I see?

If issue tracking was decentralized, you don't know if everyone else sees the same thing as you do. With Github there's a chance that they are down ("degraded service" as they call it), but if it works, you press refresh, and you know you're on the same page as everyone else.

Re: GitHub Is Down?

#38

Post by diggan »

jakobegger wrote: post #37
diggan wrote: post #35

Earlier quoted context omitted.

I agree, I wouldn't want to have merge conflicts in issues/PRs either, but I don't think just because it's decentralized, means that it would have conflicts. A quick thought would be to have issues/PRs only editable by the author via signing for example. Not allow any edits and just modifications on top of other modifications. Is there a reason you prefer centralization that is not about conflicts?

Knowing that everyone sees what I see? If issue tracking was decentralized, you don't know if everyone else sees the same thing as you do. With Github there's a chance that they are down ("degraded service" as they call it), but if it works, you press refresh, and you know you're on the same page as everyone else.

Ah, I see. Thanks for elaborating!

Yeah, true that it could be an obstacle. I wonder if the UX of any application for this could solve that by showing indicators of when the last data was fetched/sent, so users could know about possible stale-content.

I guess the problem of "everyone else sees the same thing as you do" is also a part of Git, where everyone keeps their own copy + a link to upstream. Seems to work well, wonder if we could possibly do the same with issues/PRs.

Post reply on HN