This is a smart move.
Gives developers who have small indy projects a reason to use Github rather than a competitor (I know I use gitlab precisely because it's free for my private one-off repos).
Gives developers who have small indy projects a reason to use Github rather than a competitor (I know I use gitlab precisely because it's free for my private one-off repos).
https://github.com/marketplace/azure-pipelines
* in marketplace, limitations apply
Why on earth are there so many domains in their login flow? My password manager can't make heads nor tails of it 90% of the time
I was working on Outlook stuff at my previous job and it was a nightmare. They have three different offerings of emails. You can login in Outlook and O365 with the same account iirc, but not the others. Or something like that.
I just remember wanting to cry as I tried to figure out how to login.
Then the API docs are even worse. They had different APIs for each email offering and one pointed to the other then that one pointed to the previous one.
Microsoft's problem is that it has too many services. Google may change things constantly but at least they don't have three different email offerings with three different APIs at varying levels of brokeness.
Other than that, their CI system is quite amazing!
GitHub's default path for organizations is that you are creating a business that will be very separate from your personal account.
GitLab's default path is that it's just a group. Maybe just a named group for related projects. Once you dig in though, GitLab's group admin is much better than GitHub in my opinion.
Edit: typo
I'm not sure how relevant it is to you, but I hope you take some inspiration from https://platform.sh/ – it's the PaaS I've had the most luck with. While it isn't perfect, it's the closest thing I've found so far. Their "almost everything is in git" and instant environment cloning are fantastic features.
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.
Assuming you're not using Issues or anything non-portable.
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.
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.
I'm wondering what the future holds for both GitHub and Azure DevOps. I actually use both, and have done for several years, and they're both great products - I'd hate for either of them to go away.
They'd be better off killing one product or the other, rolling it into the remaining one, and at least having a single-brand offering that can compete on features with GitLab.
I'm afraid you're mistaken there - Azure DevOps combines Git (or TFVC, if you really must!) repos with CI, CD and scrum/kanban boards.
GitLab is GitHub but with more features and a smaller community. GitLab focuses more on code than community, at least from my experience with it.
Changing the terminology makes me not want to use gitlab.
Take a new dev who has never used gitlab or git. Merge request instantly makes sense but pull request does not.
But... But... Yes, I have no good arguments, but after 10 years of saying pull-requests anything else feels wrong.