I’m embarrassed that I haven’t been able to figure this out for myself, but all the tutorials I’ve found so far focus too much on the logistics of the UI and don’t really explain a realistic, relevant workflow.
Here’s my situation: I’m a solo developer writing mostly C (a little C++ as I learn) embedded code for an Arduino-like microcontroller (Teensy 4). I recently switched to the Visual Studio Code environment (but I’m far from an expert on that), using the PlatformIO add-on for framework/library management. My largest project contains about 20 source modules and associated header files, and I’m starting to reuse and modify modules for reuse on subsequent projects. The lack of any formal revision control is starting to cause headaches, and that led me to explore Github.
I’m not even sure what questions to ask, but here’s a start:
- What are the differences between Github and Github desktop?
- Does using Github desktop imply that repositories are stored locally vs. in the cloud? Both?
- Should I use one repository per project, or should I create a separate repository for modules that I think will be reused across projects?
- Should the fact that I’m using VS Code influence my thinking about how to organize repositories?
Thanks for any help you can provide, including pointing me to articles/tutorials that are actually relevant to my situation.
submitted by /u/Aerokeith