Live data from Hacker News

Think Twice Before Downgrading to a Free GitHub Account

blog.jaredsinclair.com

31–40 of 102 posts

Re: Think Twice Before Downgrading to a Free GitHub Account

#32

For what it's worth, protected branches are pretty clearly listed as a "Github Pro" feature in their pricing page. I agree that it'd be nice if they warned you about features you're using that will be turned off, but I don't think it's unreasonable to expect that people requesting downgrades understand which features are in which plan. Maybe this could be suggested to GitHub's Paperclips project, to avoid future conf…

Agreed. But there were a lot of people celebrating GitHub’s recent free account changes who were saying you no longer needed the pro account; this is a good reminder that you may need the pro account after all and do that check.

Re: Think Twice Before Downgrading to a Free GitHub Account

#35

For what it's worth, protected branches are pretty clearly listed as a "Github Pro" feature in their pricing page. I agree that it'd be nice if they warned you about features you're using that will be turned off, but I don't think it's unreasonable to expect that people requesting downgrades understand which features are in which plan. Maybe this could be suggested to GitHub's Paperclips project, to avoid future conf…

Agreed. But there were a lot of people celebrating GitHub’s recent free account changes who were saying you no longer needed the pro account; this is a good reminder that you may need the pro account after all and do that check.

Downgrading an account for free should always be treated the same as upgrading an account for money. You gotta consider what you gain and lose in doing so before pulling the trigger without looking first.

Re: Think Twice Before Downgrading to a Free GitHub Account

#37
post #9

Earlier quoted context omitted.

Exactly. Git and github aren't backup tools. I always feel like github (and others) added to the git workflow things that are bolted on top of it and tie you to their platform.

Slightly offtopic, I have always considered a strange failure of git that branches are second class citizen in git, not worthy of the same versioning mechanisms as files. It is not unreasonable to expect a versioning system to be able to track the history of branches. And if I don't want to loose a file, just because it was deleted some time in the past, surely I also don't want to loose a branchjust because it was d…

[deleted]

Re: Think Twice Before Downgrading to a Free GitHub Account

#38

honestly though... how many everyday devs actually use something like this?

If you have a job where you arent allowed to commit directly to master / development branches this is probably how they enforce it. It keeps juniors from pushing bad code without peer review. It forces developers into doing PRs instead. Protected branches are the first thing we setup when we make a new repository at work once we hit the "getting good enough for production and autobuilds" stage of development.

Re: Think Twice Before Downgrading to a Free GitHub Account

#39

Gitlab has private repos for free and the service is imho on par with github

As does BitBucket which I prefer just because it matches what I use at work. I also keep a GitLab for backup type reasons.

Also Bitbucket supports mercurial repositories, which is a shame has so little support on the other big platforms.

Re: Think Twice Before Downgrading to a Free GitHub Account

#40
post #39

Earlier quoted context omitted.

As does BitBucket which I prefer just because it matches what I use at work. I also keep a GitLab for backup type reasons.

Also Bitbucket supports mercurial repositories, which is a shame has so little support on the other big platforms.

Git won though. I'm not especially a fan of git, but at this point advocating for mercurial is tilting at windmills.
Post reply on HN