So I’m working on creating some new VCS and PROS documentation for my programmers. A lot of them haven’t done full on C++ work, and for my more experienced ones, we’ll be using PROS to get the most out of robots.
Something I wanted to teach this year though, was good version control, namely git. Think it’s not only useful for the teams to know down the line, but they could keep their files better organized than what we had last year (Google Drive but no one kept the same consistent name/date format).
I have the equipment to run a local git server at any competition we go to.
So for those who used git or even other version control systems, how’d you implement it for your teams?
Personally I’ve used github + github client with the repo inside a dropbox folder. This year I’ll likely switch to gitKraken client + gitlab server at my house, still using dropbox.
If you’re using PROS, and your programmers don’t have command line git experience, I would recommend they use VSCode. It has visual git built-in, and you can run PROS CLI in the integrated terminal. If you’re associated with a school, you can get a free GitHub education organization with unlimited private repos, if that’s something that concerns you.
Most don’t have command line experience.
I actually edited my VS Code to be add buttons for running PROS CLI commands that I plan on sharing with my teams.
I’ve also had recommendations of SVN. I use both at my job, so I’m just thinking of different ways teams have used one or the other effectively.
Purdue’s team uses command line git almost exclusively, I’ve found that getting college students acquainted with the command line and basic git functionality is fairly straightforward.
With the high school team that I’ve mentored, I found that using GitKraken was a better solution. It’s much easier to explain the concepts behind Git without having to also explain the command line. Atom and VS Code both have git guis built in, but GitKraken has worked well in my experience.
Ya I second GitKraken, its simple to use and I still use it for most of my workflow. I also like that it works with any OS.
Alright, took a brief look at GitKraken. Where was this when I was learning git in HS 10 years ago?
Haha exactly. I like how it scales well. If I am doing something simple like a homework assignment, similar to a single programmer working on robot code.
Or if I am doing something complicated with multiple releases, pull requests, forks, and tons of branches.
