4 ms·

I actually switched from Github to Gitlab about two months ago just for this reason. I bootstrap my company from my own pocket and wanted to save a few dollars

I actually switched from Github to Gitlab about two months ago just for this reason. I bootstrap my company from my own pocket and wanted to save a few dollars every month. Really wish I knew this was coming before I deleted the repos and migrated everything. edit -- to everyone asking, I have no problems with Gitlab and I also have no strong preference Gitlab vs Github, they both perform the same role for me in exactly the same manner. I just wish I had those couple of days back that I spent migrating and editing my deploy scripts.

phillc73 8y ago
How does this change by Github make you regret migrating to Gitlab? Do you think Gitlab's offering is in some ways inferior? I mirrored everything to Gitlab sometime ago, for public repositories and also use them for private repositories. The only real advantage I could specifically name for Github is the organic contribution factor due to their volume of traffic. However, this doesn't really apply to private repositories. Edit: I see this has been answered below now - time spent migrating.
- balls187 8y ago
  Also, Github is the defacto standard so most tooling has built-in github integrations.
eeeeeeeeeeeee 8y ago
I did the exact same thing a few weeks ago.
tebbers 8y ago
Exactly the same situation here! Dammit!
andybak 8y ago
Isn't a migration back just a git clone away? Assuming you're not using Issues or anything non-portable.
- aflag 8y ago
  That would just be more time wasting. I think he is regretting ever spending time on that.
  - freehunter 8y ago
    Yep it's the time I spent making the decision (Gitlab isn't the only other choice, and I did a bit of research), then changing my scripts to point to Gitlab instead of Github and letting a couple of testers know where to go to file issues then familiarizing myself with Gitlab's interface. Not a huge amount of time, but since I only have about 2-3 hours per day to work on the technology side of the business, it was a couple of days worth of hours from the time I decided I needed to cut spending to the time I had Gitlab integrated into my stack. It was a couple of days I didn't have to spend improving the product, even though it was a win from a financial standpoint. And now with this announcement, it was hardly even a financial win. Oh well. I don't have the time or desire to migrate back.
    - deleted 8y ago
      [deleted]
Kye 8y ago
It sounds like it was the right call at the time. You can't time corporate strategy shifts any more than you can time the market, so just make the best calls you can with what you know.

phillc73 8y ago

How does this change by Github make you regret migrating to Gitlab? Do you think Gitlab's offering is in some ways inferior? I mirrored everything to Gitlab sometime ago, for public repositories and also use them for private repositories. The only real advantage I could specifically name for Github is the organic contribution factor due to their volume of traffic. However, this doesn't really apply to private repositories. Edit: I see this has been answered below now - time spent migrating.

balls187 8y ago
Also, Github is the defacto standard so most tooling has built-in github integrations.

eeeeeeeeeeeee 8y ago

I did the exact same thing a few weeks ago.

tebbers 8y ago

Exactly the same situation here! Dammit!

andybak 8y ago

Isn't a migration back just a git clone away? Assuming you're not using Issues or anything non-portable.

aflag 8y ago
That would just be more time wasting. I think he is regretting ever spending time on that.
- freehunter 8y ago
  Yep it's the time I spent making the decision (Gitlab isn't the only other choice, and I did a bit of research), then changing my scripts to point to Gitlab instead of Github and letting a couple of testers know where to go to file issues then familiarizing myself with Gitlab's interface. Not a huge amount of time, but since I only have about 2-3 hours per day to work on the technology side of the business, it was a couple of days worth of hours from the time I decided I needed to cut spending to the time I had Gitlab integrated into my stack. It was a couple of days I didn't have to spend improving the product, even though it was a win from a financial standpoint. And now with this announcement, it was hardly even a financial win. Oh well. I don't have the time or desire to migrate back.
  - deleted 8y ago
    [deleted]

Kye 8y ago

It sounds like it was the right call at the time. You can't time corporate strategy shifts any more than you can time the market, so just make the best calls you can with what you know.