Think Twice Before Downgrading to a Free GitHub Account
21–30 of 102 posts
Re: Think Twice Before Downgrading to a Free GitHub Account
#22Re: Think Twice Before Downgrading to a Free GitHub Account
#23What? 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
Re: Think Twice Before Downgrading to a Free GitHub Account
#24> 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.
Re: Think Twice Before Downgrading to a Free GitHub Account
#25Earlier quoted context omitted.
Come the next garbage collect, the file changes in a deleted branch are forgotten. If I don't want to loose changes, garbage collect shouldn't be a thing, because there is no garbage, just history.
As I recall the GC will only touch things that have been deleted for some time (a month?), that's a long time to correct accidental deletions. Garbage is created every time you amend or rebase. What is the value of keeping around commits that are unreachable through any branch, containing typos in the commit messages? It seems to me that source control can really bring out the hoarder in people, a fear of throwing aw…
That is what I mean by second class citizen. The same logic doesn't apply to deleted files in a branch. If I delete a file it may not be accidental at all, and still I expect it to be accessible and not be considered 'orphaned', 'garbage' or similar. Why doesn't git throw away everything that is older than 90 days? (the default for gc)
Re: Think Twice Before Downgrading to a Free GitHub Account
#26I downgraded too, and noticed GitHub Pages stopped working (the content is still there, but they don't rebuild - although they did for a little while after downgrading). It is clearly marked as a Pro feature, I just hadn't considered that the free private repos would be more restricted. It's not a big deal to me, I'll probably just make the repos public.
Re: Think Twice Before Downgrading to a Free GitHub Account
#27> 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.
Cloud backup (Backblaze etc.) is for when my house is on fire. But the only backups I actually trust are the ones that I have 100% control over.
Re: Think Twice Before Downgrading to a Free GitHub Account
#28[0] https://docs.gitlab.com/ee/user/project/protected_branches.h...
Re: Think Twice Before Downgrading to a Free GitHub Account
#29I downgraded too, and noticed GitHub Pages stopped working (the content is still there, but they don't rebuild - although they did for a little while after downgrading). It is clearly marked as a Pro feature, I just hadn't considered that the free private repos would be more restricted. It's not a big deal to me, I'll probably just make the repos public.
Do you mean some specific additional features for GitHub Pages, such as a vanity URL, or building from private repos?
Re: Think Twice Before Downgrading to a Free GitHub Account
#30I downgraded too, and noticed GitHub Pages stopped working (the content is still there, but they don't rebuild - although they did for a little while after downgrading). It is clearly marked as a Pro feature, I just hadn't considered that the free private repos would be more restricted. It's not a big deal to me, I'll probably just make the repos public.
I have a free GitHub account and also have GitHub Pages for my blog, which is developed in one of my public repos. Do you mean some specific additional features for GitHub Pages, such as a vanity URL, or building from private repos?