91–100 of 664 posts
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…
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'…
This is a great change! One request: I wish that SAML was not an enterprise feature. SAML ought be a basic security feature like 2FA—it's especially valuable for open source teams who might use a mixture of services, and an easily accessible and cheap SSO solution would go a long way in raising the security bar for all teams, not just open source teams.
Earlier quoted context omitted.
This is a great change! One request: I wish that SAML was not an enterprise feature. SAML ought be a basic security feature like 2FA—it's especially valuable for open source teams who might use a mixture of services, and an easily accessible and cheap SSO solution would go a long way in raising the security bar for all teams, not just open source teams.
Agreed. SAML even makes sense for solo dev.
Great news for everyone bar startups competing with them as it looks like Microsoft is turning their multi-billion acquisition of GitHub into a loss leader to get as many devs using their platform as possible, no doubt to flex seamless integrations into Azure which looks like they're executing exceptionally well with their acquisitions & new feature giveaways. From the side-lines it looks like they're slowly becoming…
I'm not complaining; MS should point GH at where the money is and there is competition you can switch to. I'm just not excited to save a few bucks a month given what will likely change.
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'…
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?
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.
For those wondering "what makes it worth paying now?", GitHub briefly addresses that: Teams who need advanced features (like code owners), enterprise features (like SAML), or personalized support can upgrade to one of our paid plans.
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…
Why would protected branches go away?
Earlier quoted context omitted.
GitHub has significant vendor lock-in, so it makes sense to make it free to capture the market before a competitor gets traction. [Speculation:] Perhaps they've run the numbers and can figure out that they make enough money from enterprise clients and will make enough more money from the 'marketplace' being a channel for selling github integrations and addons to cover this cost of not trying to monetize through suppo…
> GitHub has significant vendor lock-in Do they? Unless you're on GitHub Enterprise, migrating is just moving your repos over the weekend, setting up new webhooks, emailing everyone a command to switch their upstream URL, and hoping the new workflow works for you. For teams of <100, this it one of the easier transitions to make.
Earlier quoted context omitted.
Hey Nat -- quick Q, with this change, is there any need for individual developers to pay for "Pro" accounts? Or did the benefits of a "Pro" account just get covered by the "Free" plan?
It looks like pro accounts have vanished? I can't find them anywhere; I assume we just won't be charged from here on out?