5 ms·

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, 20

by dmw_ng 7y ago

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 private repos Code review automatic assignment in private repos Scheduled reminders in private repos Standard support 2,000 minutes for GitHub Actions (currently 3,000) 500MB of storage for packages (currently 2GB)

markphip 7y ago
Why would protected branches go away?
- jswny 7y ago
  They are still a premium only feature.
  - markphip 7y ago
    OK.. maybe it is terminology then because Free public repos have Branch Protection rules. Do you not have those with Free private repos? Or is "Protected Branches" some bigger feature?
    - alecbenzer 7y ago
      > Do you not have those with Free private repos? Correct.
- tomduncalf 7y ago
  There's a more detailed table at the bottom of https://github.com/pricing https://github.com/pricing
j88439h84 7y ago
I hope GitHub allows protected branches in private repos. They're really important for everyone, not just enterprises.
- Ayesh 7y ago
  They do, even at $4/mo/user plan.
closeparen 7y ago
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 pretty roundabout.
- RandallBrown 7y ago
  This sounds like how my previous company had GitHub configured. We couldn't push to master, but we could merge accepted PRs. Not sure if this was done with GitHub or with Git itself.
  - tedivm 7y ago
    Generally speaking that's what Github's "protected branches" are, and it looks like you lose those for private repos when you switch to the free plan.
- judge2020 7y ago
  Protected branches are the gateway to the multi-PR-review requirement, so you'd need the $4 GH Teams.

by dmw_ng 7y ago

markphip 7y ago

Why would protected branches go away?

jswny 7y ago
They are still a premium only feature.
- markphip 7y ago
  OK.. maybe it is terminology then because Free public repos have Branch Protection rules. Do you not have those with Free private repos? Or is "Protected Branches" some bigger feature?
  - alecbenzer 7y ago
    > Do you not have those with Free private repos? Correct.
tomduncalf 7y ago
There's a more detailed table at the bottom of https://github.com/pricing https://github.com/pricing

j88439h84 7y ago

I hope GitHub allows protected branches in private repos. They're really important for everyone, not just enterprises.

Ayesh 7y ago
They do, even at $4/mo/user plan.

closeparen 7y ago

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 pretty roundabout.

RandallBrown 7y ago
This sounds like how my previous company had GitHub configured. We couldn't push to master, but we could merge accepted PRs. Not sure if this was done with GitHub or with Git itself.
- tedivm 7y ago
  Generally speaking that's what Github's "protected branches" are, and it looks like you lose those for private repos when you switch to the free plan.
judge2020 7y ago
Protected branches are the gateway to the multi-PR-review requirement, so you'd need the $4 GH Teams.