Live data from Hacker News

GitHub is now free for teams

github.blog

471–480 of 664 posts

Re: GitHub is now free for teams

#471

Hi HN, I'm the CEO of GitHub. Everyone at GitHub is really excited about this announcement, and I'm happy to answer any questions. We've wanted to make this change for the last 18 months, but needed our Enterprise business to be big enough to enable the free use of GitHub by the rest of the world. I'm happy to say that it's grown dramatically in the last year, and so we're able to make GitHub free for teams that don'…

nice play. rigth out of Microsoft playbook.

in a time where competiton is triving and github is not synonymous of opensource anymore, offer free stuff to embrace (fake you still support opensource), extend (offer cpu time), extinguish (kill the budding competition before they can establish themselves)

I guess you asked for a question, so here is one: which of these true open source supporters are you more afraid of:

gitlab?

codeberg?

others we should know about?

thank you!

Re: GitHub is now free for teams

#472
post #295

Earlier quoted context omitted.

I think it depends on OS (Linux is $0.008/Minute, but macOS is a lot more - like $0.08): https://github.com/features/actions (scroll to the bottom)

Ok, so that'd cost me USD$56, leading to a higher monthly than previous pricing. So, steering users toward the Action landscape is obviously a better monetization model.

Just got an email from Github. Money quote:

> For more than 99% of customers, these changes have lowered their GitHub bills, in many cases quite dramatically. For a very small number of customers who use a large percentage of the free Actions minutes allotment each month, these changes have the potential to cause your bill to increase by $20-50/month, depending on how much you use Actions in the future. To offset that possibility, we’re adding a free credit of $500 to your organization’s GitHub account for you to use in any way you want.

Re: GitHub is now free for teams

#473

Earlier quoted context omitted.

Hi Nat, with Microsoft now owning Github, I'm really curious to know what the future holds for both Azure DevOps and Github? I'm a user of both - Github for OSS, and Azure DevOps for private work. IMO, these areas are where they are best suited - pipelines in particular are really powerful in Azure DevOps, and user/permission management, AAD integration and integration with build agents are all excellent. I really li…

Both products have a bright future and millions of users, and so we're continuing to invest in both for the foreseeable future. We're also finding ways to improve integration between them, so people can use them together if they want to. GitHub Actions reuses a bunch of code from Pipelines under the hood, for example.

After listening to episode 321 of The Azure Podcast[0] my understanding was that Azure DevOps would eventually be phased out; question begins at ~10:30 and at about ~12:00 a rough timeline of 5 years was given with guidance to select GitHub if just starting out.

0: http://azpodcast.azurewebsites.net/post/Episode-321-GitHub

Re: GitHub is now free for teams

#475

Earlier quoted context omitted.

Then again there is this list of 346 discontinued Microsoft products, some of which had very short lifespans: https://www.versionmuseum.com/history-of/discontinued-micros...

Yes, I would definitely hate to trust Microsoft with my enterprise software build pipeline because of how they refused to support Microsoft Bob.

Well, probably not because of Bob, but their cloud based offerings have make me wonder about trust.

- Business Contact Manager for Outlook, Outlook Customer Manager

- Microsoft Invoicing, Listings etc.

And these are critical applications for a company.

Have a look at Sharepoint which is widely used and has an uncertain future. Or the strategy behind Lync, Skype and now teams.

But we'll see. Microsoft has shifted in a good way in the last couple of years but their track record in keeping legacy operating system APIs for decades is not necessarily a good indicator of the stability of their other product lines.

Re: GitHub is now free for teams

#476
post #315
post #197

Earlier quoted context omitted.

Thanks for the kind words! For developers everywhere competition is great. We recently made 18 new features free and open source https://about.gitlab.com/blog/2020/03/30/new-features-to-cor... and today Github with an improved free plan and their team plan came down to the exact same price as our most affordable plan. BTW Maybe an idea to rename their lowest tier from team, may we suggest bronze? :) Since you mention…

One big differentiator that GitHub has vs GitLab is the availability of monthly pricing. This was a deal breaker against GitLab for us.

Thanks for your inputs! Offering the flexibility of monthly pricing to our customers is definitely one of our priorities. We are currently working on optimizing the online portal to ensure our customers have a seamless experience when monthly pricing is available.

Re: GitHub is now free for teams

#477
post #79

Earlier quoted context omitted.

Not true. There are other things (like audit logs, invoice/PO payments, better support) that enterprises will still want.

Yeah but considering SAML is one of the primary asks of enterprise, it kind of makes it a big selling point.

And people keep saying that it's a security feature but that's not why large orgs pay for it. It's a "I'll pay you to not have to manually manage account access to all these different services.

Re: GitHub is now free for teams

#478

Earlier quoted context omitted.

The YAML configuration is something I have to learn that provides no value-add outside of GitHub. If it was at least based on Docker, you could re-use existing technical knowledge or teach people something that's valuable in other contexts.

A lot of things use YAML for configuration... what would you prefer for configuration? XML?

I want to write a Dockerfile. I don't particularly have an issue with YAML.

Re: GitHub is now free for teams

#479

Earlier quoted context omitted.

Agreed. SAML even makes sense for solo dev.

So you care a lot about this, but not $4/month care?

Right but $5/month/service is where it starts to add up. Unless you're managing hundreds of users across a bunch of disparate services the value/cost doesn't work out in your favor.

Re: GitHub is now free for teams

#480
post #63

This is an awesome change! In case anyone else was wondering, here's what you lose by cancelling: You are downgrading to GitHub Free After April 15, 2020, ... features and limits will change: Protected branches in private repos Draft PRs in private repos GitHub Pages in private repos (using 1) Wikis in private repos Code owners in private repos Multiple issue assignees in private repos Multiple PR assignees in privat…

It's not clear to me whether this is possible under any configuration, but: can you enforce a two-person rule? I'd like all users to be able to merge accepted PRs, but no one should be able to push directly to master (unless an admin specifically elevates permissions to do that). The only way I can think of is to have a bot be the only one with commit access, and to interact with the bot to do merging. But that seems…

Protected branches are the gateway to the multi-PR-review requirement, so you'd need the $4 GH Teams.
Post reply on HN