3 ms·
You can have a private repo called writing with a folder for each project. Not elegant but it works...
by robszumski 13y ago
You can have a private repo called writing with a folder for each project. Not elegant but it works...
- theboss 13y agoYeah that does work. It is only frustrating when I have a lot of big projects at the same time. Sometime they can be public, but othertimes they cant. I imagine it is worse for undergrads, where almost all their coursework will be private.
- Fomite 13y agoThis too. I have an "Archive" folder, and before that one called "Dissertation" which was in reality like, 8 different projects.
- theboss 13y agoThis is a good solution. Have a archive private repo that everything I'm done with goes in. Perfect.
- jackowayed 13y agoI just git clone old projects into a Dropbox private folder. I can easily keep the whole repo history even if there are multiple branches, but it doesn't take up GitHub usage at all. Of course, if you had Issues or the like, none of these solutions really work. I do wish GitHub had a way to deactivate projects to save money. Maybe put it in a read-only state, still count it against your disk quota, but you'd have to make it active to actively work on it and update it. I feel like a lot of systems do similar things (eg. charge per user but allow deactivating users in case they go on leave or quit but may return--pause paying for that user without losing the data in case you want to reinstate.)