Not using a repository exposes you to several risks.
The largest of which is code disappearing with no copies.
So build your first repository on github to back yourself up in a place with a far lower risk .
The next problem is staying in step with the master project. Adding the inevitable updates from Control-Surface will become a very manual job.
Really you want to work on a fork of the original repo, which can handle all the update stuff for you.
So that might well be the second repo you establish to allow you to check the changes.
You are not walking a path that many haven’t worked before It’s a classic success problem, so congratulate yourself on your success!
I will of course be steal…, borrowing large parts of this with your permission, if only to hear @riban chuckling about me writing in C . .
Most of the repository stuff involves remembering exact names of things … . .
I’m new to arduino, but have the ide running with a mkrzero ( I don’t know if the codes ok on this device for some arduino-esque reason, but am pushing on regardless…)