Live data from Hacker News

Think Twice Before Downgrading to a Free GitHub Account

blog.jaredsinclair.com

1–10 of 102 posts

Re: Think Twice Before Downgrading to a Free GitHub Account

#5
post #4

> I live in mortal fear of making a dumb mistake and losing irreplaceable source code. Then store backups of your repositories somewhere else than GitHub.

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.

Re: Think Twice Before Downgrading to a Free GitHub Account

#6
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 confusion?

Re: Think Twice Before Downgrading to a Free GitHub Account

#9
post #4

> I live in mortal fear of making a dumb mistake and losing irreplaceable source code. Then store backups of your repositories somewhere else than GitHub.

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 deleted. I don't buy the 'I want to be able to hide f-ups' argument.

Re: Think Twice Before Downgrading to a Free GitHub Account

#10
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…

Doesn’t the reflog serve that purpose though? Branches are just labels for a commit, and all commits (and names) are visible in the reflog.
Post reply on HN