5 ms·

I'm just wrapping up the work to migrate my company away from Gitlab to Github and this happens. I did it because I figured Github has to have better reliabilit

I'm just wrapping up the work to migrate my company away from Gitlab to Github and this happens. I did it because I figured Github has to have better reliability / uptime than Gitlab. Someone joked that as soon as the migration is done Github will have some major downtime. sigh

deleted 7y ago
[deleted]
benceno 7y ago
You can't spell GitLab and GitHub, so you deserve it.
- celticninja 7y ago
  If we are being pedantic they were both spelled correctly.
- shhsshs 7y ago
  HN is not typically receptive to snide corrections/remarks. There are several more productive ways to address a minor capitalization error - the best of which is to not correct it at all because it's so trivial and unimportant.
  - hombre_fatal 7y ago
    Besides, why would I care if how I capitalize a company's name isn't perfectly in line with their marketing style guide? Github is lucky if I even feel like capitalizing the first letter. What a weird thing to hold over others.
    - benceno 7y ago
      OK I AM SORRY
q3k 7y ago
I highly recommend running at least a local, self-hosted git mirror at any tech company, just in these cases. Gitolite + cgit are extremely low maintenance, especially if you host them next to your other production services. Not to mention, if you get the self-hosted route you can use Gerrit, which is still miles better for code review than GitHub, Gitlab, bitbucket and co.
- grey-area 7y ago
  You don't even need gitolite, if you're going the self-hosted route: apt install git-all is enough to host your own git server. Put it behind a firewall to limit access and use standard linux users with ssh keys for access control if you don't need anything fancy. For small companies I'm not sure you need anything else. Of course if you need different levels of access etc then you'll need more sophisticated tools, but many people won't. Code review I do using local tools (the editor) face to face, again not sure you need an online service for that unless you're a larger company with lots of developers coordinating (in which case it becomes pretty essential).
  - q3k 7y ago
    > Code review I do using local tools (the editor) face to face, again not sure you need an online service for that unless you're a larger company with lots of developers coordinating (in which case it becomes pretty essential). I mostly like online code review services because they offer an audit trail and semantic history that's easier to navigate than email. And of course, to let CI automation check tests, coverage and lint. Not because I don't trust my coworkers, but because otherwise I would forget to run tests and lint myself.
    - grey-area 7y ago
      Lots of different ways to do it, and of course github and online code review is tremendously useful to people, particularly on large projects with lots of collaborators, and where a history of reviews is required. For lots of small projects though, it's perhaps not as necessary as people think. I run tests and linting locally on save and don't really use the code review/CI features of online hosts much. That won't suit everyone of course, but it is one possible path.
tauchunfall 7y ago
>I did it because I figured Github has to have better reliability Have you looked at the GitHub incident history? https://www.githubstatus.com/history https://www.githubstatus.com/history
swebs 7y ago
>I did it because I figured Github has to have better reliability / uptime than Gitlab Why the hell would you think that after the Microsoft acquisition?

deleted 7y ago

[deleted]

benceno 7y ago

You can't spell GitLab and GitHub, so you deserve it.

celticninja 7y ago
If we are being pedantic they were both spelled correctly.
shhsshs 7y ago
HN is not typically receptive to snide corrections/remarks. There are several more productive ways to address a minor capitalization error - the best of which is to not correct it at all because it's so trivial and unimportant.
- hombre_fatal 7y ago
  Besides, why would I care if how I capitalize a company's name isn't perfectly in line with their marketing style guide? Github is lucky if I even feel like capitalizing the first letter. What a weird thing to hold over others.
  - benceno 7y ago
    OK I AM SORRY

q3k 7y ago

I highly recommend running at least a local, self-hosted git mirror at any tech company, just in these cases. Gitolite + cgit are extremely low maintenance, especially if you host them next to your other production services. Not to mention, if you get the self-hosted route you can use Gerrit, which is still miles better for code review than GitHub, Gitlab, bitbucket and co.

grey-area 7y ago
You don't even need gitolite, if you're going the self-hosted route: apt install git-all is enough to host your own git server. Put it behind a firewall to limit access and use standard linux users with ssh keys for access control if you don't need anything fancy. For small companies I'm not sure you need anything else. Of course if you need different levels of access etc then you'll need more sophisticated tools, but many people won't. Code review I do using local tools (the editor) face to face, again not sure you need an online service for that unless you're a larger company with lots of developers coordinating (in which case it becomes pretty essential).
- q3k 7y ago
  > Code review I do using local tools (the editor) face to face, again not sure you need an online service for that unless you're a larger company with lots of developers coordinating (in which case it becomes pretty essential). I mostly like online code review services because they offer an audit trail and semantic history that's easier to navigate than email. And of course, to let CI automation check tests, coverage and lint. Not because I don't trust my coworkers, but because otherwise I would forget to run tests and lint myself.
  - grey-area 7y ago
    Lots of different ways to do it, and of course github and online code review is tremendously useful to people, particularly on large projects with lots of collaborators, and where a history of reviews is required. For lots of small projects though, it's perhaps not as necessary as people think. I run tests and linting locally on save and don't really use the code review/CI features of online hosts much. That won't suit everyone of course, but it is one possible path.

tauchunfall 7y ago

>I did it because I figured Github has to have better reliability Have you looked at the GitHub incident history? https://www.githubstatus.com/history https://www.githubstatus.com/history

swebs 7y ago

>I did it because I figured Github has to have better reliability / uptime than Gitlab Why the hell would you think that after the Microsoft acquisition?