3 ms·

for those saying you can't access your code, don't you all have a copy sitting on your computer in front of you? How do you use github as source control in a wa

for those saying you can't access your code, don't you all have a copy sitting on your computer in front of you? How do you use github as source control in a way that means when github goes down there's no code to work on?

csours 3y ago
I have a doco change to make. I just need to paste it into the browser editor and do a PR. Can't do push or pr right now.
reactordev 3y ago
git pull fails to work. The code you checked in last night and now are wanting to pull to your “copy sitting on your computer” can no longer happen, rendering your local copy stale. Do you work on stale code? Accessing code could also refer to them in their roles: maybe they are DevOps and their job is to wire up pipelines to deploy spaghetti to a giant furball k8s environment and they can’t because they can’t access their code. Don’t be obtuse.
deathanatos 3y ago
What does your company do that you don't have Github or some equivalent centralization, such as Gitlab, self-hosted or not? For the rest of us, Github (/etc.) is our primary means of transferring branches, a centralized "main" branch, and sometimes where CI/builds/test happen, as well as deployments. This isn't even bizarre … I've worked at 6+ companies now, and 100% of them followed this pattern. (Not all with Github, but they all had some centralized place to push/pull code and conduct reviews, tests, deployments…) (I'd entertain the usual "is self-hosted worth it?" argument that tends to crop up in these threads. But this question is a bit off the wall.) I can still commit to my local repository, of course, but at some point, I am going to need to share my work with coworkers or with production. During a normal day, that's several times per day, as features/branches are done & go out for review & merging…
- hotnfresh 3y ago
  Even the two places I've worked that self-hosted bare git repos on cheap Linux VMs (both times, due to management concern about Github snooping on private code), no fancy web UI or anything, it was used the same way GH is, with the server acting as the hub for collaboration.

csours 3y ago

I have a doco change to make. I just need to paste it into the browser editor and do a PR. Can't do push or pr right now.

reactordev 3y ago

git pull fails to work. The code you checked in last night and now are wanting to pull to your “copy sitting on your computer” can no longer happen, rendering your local copy stale. Do you work on stale code? Accessing code could also refer to them in their roles: maybe they are DevOps and their job is to wire up pipelines to deploy spaghetti to a giant furball k8s environment and they can’t because they can’t access their code. Don’t be obtuse.

deathanatos 3y ago

What does your company do that you don't have Github or some equivalent centralization, such as Gitlab, self-hosted or not? For the rest of us, Github (/etc.) is our primary means of transferring branches, a centralized "main" branch, and sometimes where CI/builds/test happen, as well as deployments. This isn't even bizarre … I've worked at 6+ companies now, and 100% of them followed this pattern. (Not all with Github, but they all had some centralized place to push/pull code and conduct reviews, tests, deployments…) (I'd entertain the usual "is self-hosted worth it?" argument that tends to crop up in these threads. But this question is a bit off the wall.) I can still commit to my local repository, of course, but at some point, I am going to need to share my work with coworkers or with production. During a normal day, that's several times per day, as features/branches are done & go out for review & merging…

hotnfresh 3y ago
Even the two places I've worked that self-hosted bare git repos on cheap Linux VMs (both times, due to management concern about Github snooping on private code), no fancy web UI or anything, it was used the same way GH is, with the server acting as the hub for collaboration.