Did someone really just write a blog post on not downgrading an account without knowing what you're doing? Yes, you should not do that. You also shouldn't buy something without knowing what you're paying for, shouldn't vote for something you don't know what it is, you shouldn't eat stuff which might be poisonous but don't know for sure, you shouldn't cross a street without looking, gosh you certainly shouldn't drive a car with closed eyes not knowing where you're driving. Let's remind everyone of these things regularly, as this stuff is apparently not obvious anymore in 2019.
Think Twice Before Downgrading to a Free GitHub Account
41–50 of 102 posts
Re: Think Twice Before Downgrading to a Free GitHub Account
#42I think it's stupid that GitHub stores (meta-) data in a place that's not governed by git. Everything should be in git.
Re: Think Twice Before Downgrading to a Free GitHub Account
#43Gitlab has private repos for free and the service is imho on par with github
I agree, and quite like Gitlab, but Github's recent decision to allow free private repos has surely put a bit of a dent in Gitlab/Bitbucket's marketshare expansion - many people were using those services instead of Github just for that feature.
Re: Think Twice Before Downgrading to a Free GitHub Account
#44Did someone really just write a blog post on not downgrading an account without knowing what you're doing? Yes, you should not do that. You also shouldn't buy something without knowing what you're paying for, shouldn't vote for something you don't know what it is, you shouldn't eat stuff which might be poisonous but don't know for sure, you shouldn't cross a street without looking, gosh you certainly shouldn't drive…
its never been "obvious" in any point in history
Re: Think Twice Before Downgrading to a Free GitHub Account
#45honestly 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.
> It keeps juniors from pushing bad code without peer review.
It keeps all developers from pushing code without peer review.
(In my experience, it’s just as often senior devs pushing broken code because “this was a simple change, why does it need review?” and it in fact being broken. Furthermore, doing PRs is not solely to “check for mistakes”, they are also used for knowledge sharing, among other reasons)
Re: Think Twice Before Downgrading to a Free GitHub Account
#46FWIW, Branch protection looks like it's a free feature on Gitlab [0] [0] https://docs.gitlab.com/ee/user/project/protected_branches.h...
That's right, it's available in both free (SaaS) and core( self hosted) tiers.
Re: Think Twice Before Downgrading to a Free GitHub Account
#47What? What is he doing that it makes him fear code loss?
git push --force It doesn't actually delete the commits, but you can't find them anymore if you don't remember the hash of the former head commit of the branch
As ComputerGuru and Schnouki explain, one can use the reflog. For anyone who's intimidated by the reflog, perhaps my recipe under "All the things your branch has ever been" will help.
Re: Think Twice Before Downgrading to a Free GitHub Account
#48Did someone really just write a blog post on not downgrading an account without knowing what you're doing? Yes, you should not do that. You also shouldn't buy something without knowing what you're paying for, shouldn't vote for something you don't know what it is, you shouldn't eat stuff which might be poisonous but don't know for sure, you shouldn't cross a street without looking, gosh you certainly shouldn't drive…
> shouldn't vote for something you don't know what it is
Isn't the whole point of democracy "a large enough volume of ignorance will average out to something sensible"? :P
Re: Think Twice Before Downgrading to a Free GitHub Account
#49For 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…
I read this post as a sharing of a confusion/assumption made. Not everyone reads fine print or manual, but ha will read HN.
Re: Think Twice Before Downgrading to a Free GitHub Account
#50Hosting private repositories on GitHub pages is another feature only available with the Pro plan. Figured this one out a few days after canceling my subscription.
It’s free on gitlab.com and you can have as many as you want. I recently parked about 10 domains there.