Live data from Hacker News

GitHub is now free for teams

github.blog

151–160 of 664 posts

Re: GitHub is now free for teams

#151
post #81

Earlier quoted context omitted.

I feel like anyone who lived through the 90s could have expected "these kinds of results". Git is open source and widely supported, which doesn't benefit Microsoft. By causing GitHub-specific features to be an essential part of a "modern" or "industry standard" git workflow, they can capture more marketshare/attention, and cause alternatives to be sidelined. This requires removing all friction to entering the proprie…

I might buy the conspiracy theory except for the fact that Azure DevOps exists and provides all the features of GitHub already with none of the restrictions you've mentioned except that you pay for the service.

Can it really be called a conspiracy theory when there is proof that MS has done this same sort of thing in the past? Past behavior is a good predictor of future behavior. Saying that someone has been shown to do something in the past, therefore it is likely that they will do the same thing in the future doesn't seem to qualify as a conspiracy theory.

Re: GitHub is now free for teams

#152

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'…

Any plans for free on prem version, like Gitlab?

Re: GitHub is now free for teams

#153
post #67

Earlier quoted context omitted.

Hey Nat glad to see you here. A few days ago one of the biggest team collaborative games (Space Station 13) got banned on GitHub without a public explanation from GitHub staff, but some suspect it was because the code contained bad words and slurs. Do you know if this is why the project was banned, and will these new private team repos be subject to the same terms/rules?

Private repos are not subject to our Community Guidelines on public content, so no, we don't enforce the same rules there: https://help.github.com/en/github/site-policy/github-communi... I wasn't aware of SS13, and will look into what happened there. Content moderation at GitHub scale is hard and sometimes mistakes are made.

Do public repos that get banned have access cut off, or are they just forcibly made private?

Re: GitHub is now free for teams

#154

Does anyone remember the arbitrary actions GitHub has taken in the past few months and all the "maybe it's time to start leaving GitHub if you want to avoid getting your repositories permanently deleted?" Or is HN just as susceptible to the narrow news horizon?

Microsoft/GitHub is doing something clever this time. They know where the developers are and know that the new consumers are developers, hence 'devsumers'.

So how does Microsoft make them happy? Give 'em free stuff: Free repositories, student pack, ebooks, courses, cloud credits, etc and they come running back to GitHub. There's Sign in with GitHub which makes it easy to claim all the freebies, unlike the rest of the alternatives.

This is why the majority of developers will stay and some would realise that it will all go down and will leave Github and self-host their own git server instead.

Re: GitHub is now free for teams

#155

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'…

I'd like to share feedback on GitHub Actions. Tried it out, and the learning curve was too much. I want to use stuff I already know -- e.g., write a Dockerfile, and then GH could run it on PR builds. The "workflow" concept didn't land for me, and I hope you consider a more generalized, open-source approach to running arbitrary scripts in response to PRs being opened, merges to master, etc.

Have you tried other CI/CD platforms? Different providers use different language but the workflow concept underpins all CI/CD pipelines.

Re: GitHub is now free for teams

#156
post #44

Earlier quoted context omitted.

can you elaborate on what you mean by this? because if you're referring to requiring review approvals before a PR can be merged, that's available in the free plan (under branch protection rules).

That's odd, https://github.com/pricing mentions it as a paid option.

A feature that's available for free on public repos isn't necessarily free for private repos, it seems. The wording on the pricing page isn't very clear about this, though.

If they mean that they're now removing required reviewers for public repos in the free plan, that's definitely a big step backward I think.

Re: GitHub is now free for teams

#157

Earlier quoted context omitted.

I'd never heard of SAML before. Is it like a more complicated version of OAuth?

SAML has been around longer and handles AuthN and AuthZ OAuth only does AuthZ. I've always found OAuth more complicated because you have to combine it with other technologies to get AuthN

OpenID Connect is the standardized AuthN process built on top of OAuth. It’s “on top of” but in practice it’s a simplification if OAuth for the specific purpose of AuttN

Re: GitHub is now free for teams

#158
post #132

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'…

First of all, thank you, this is great news. That said, the news made me wonder what exactly I’m still paying for with my personal Pro account. I went to the pricing page https://github.com/pricing and it seems Pro isn’t even listed anymore? And the Billings page https://github.com/settings/billing says “Pages, Wikis, protected branches and more for Pro developers” without any further explanation or link to docs expl…

I still get a Pro option when going to https://github.com/account/upgrade from a free account, and it seems to match Teams, here's the blurb:

> Required reviewers in private repos

> Protected branches in private repos

> Repository insights in private repos

> Wikis in private repos

> Pages in private repos

> Code owners in private repos

> 3,000 minutes for GitHub Actions

> 2GB of storage for packages

Re: GitHub is now free for teams

#159

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'…

[deleted]

Re: GitHub is now free for teams

#160

I think GitHub are doing well, but one cannot deny that GitLab has carved out a fantastic niche (on-prem, private instances, OSS, etc) that GitHub doesn't compete in. So while I agree GitHub are "the" company to beat, I think GitLab is doing a good job of contrasting. PS - No affiliation with anyone.

GitHub absolutely does compete for on-prem installation.

Source: we use an on-prem installation at Vimeo

Post reply on HN