4 ms·

As a solo developer, wouldn't all these git repos be on your local machine as well? What risk are you trying to avoid? If gitlab or github is down and you hav

As a solo developer, wouldn't all these git repos be on your local machine as well? What risk are you trying to avoid? If gitlab or github is down and you have the repo locally, you don't have an issue. If you've already handed off the repo to someone else, that's on them to store it and it'll likely be under their account. I guess it's not clear from your intro what features you use 3rd party git hosting for other than backing up your repos. Are you submitting pull requests to clients? Tracking issues? Other?

petecooper 9y ago
>As a solo developer, wouldn't all these git repos be on your local machine as well? Yes, multiple machines. >What risk are you trying to avoid? I wouldn't say there's a perceived risk as such. I've run my own git infrastructure until now, and I want to stop doing that. The risks I've had were with GitLab CE updates clobbering my server (happened three times now), which then involves a few hours of rebuilding. >I guess it's not clear from your intro what features you use 3rd party git hosting for other than backing up your repos. >Are you submitting pull requests to clients? Tracking issues? Other? Tracking issues, yes - lots. Pull requests to clients, that will come very soon with external hosting. CI is not on the shopping list at this stage, but may be used if it's available.