I’m afraid that GitHub is run by Microsoft and I would consider it pretty thoroughly corporate these days

Ah. Did not know that. That’s… unfortunate.

although using it as a cloud service is basically just gonna be add all and then commit, surely? you’re not practising any other git operations if only using as cloud storage?

This is true enough actually but it helped drill the process into my head when I first started it and I found it simple enough to use after a while, esp since I just wrote a bash function to cut down on cd’ing.

but people normally do this with programming projects, which you should have no shortage of as a CS major.

You’d be surprised.

price, desire to keep out of commercial cloud providers + inability to host my own private cloud service, desire/need to be more familiar with git in general as a compsci major, and ease of use. those are pretty much the main reasons

The reason you can’t do the prior in a separate follow-up commit is that the file would still be in the git history, and hence it must be pushed to GitHub along with the rest of the repo files.

This makes sense. Is it possible to delete the offending commit completely? I use github like a cloud service for files, writing, and class notes, mostly just to push things from my laptop to my desktop and vice versa, so I’m not particularly worried about keeping commit history or anything. If not, then I’ll try out the rm method.

Out of curiosity, what advantages do you see yourself getting with robotic limbs? If I were to do a body part it would probably be spine for all around better body support.