Intro to Git & Github
So you know how to write Java code, and you know the basics of how our robot code is written. Now, you might be wondering, how do we collaborate and write code as a team? Surely, we don't take turns passing around a computer to type in our lines. Enter version control.
Here's a handy article about it. Stop at the steps, you don't need to do them.
Once you're done, we'll do some exercises to see if you've got it.
Note
We'll be using VS Code's built-in version control tools in this tutorial, but there are many other good tools too, including Sourcetree, Github Desktop, Gitkraken, and of course, the ol' command line. You don't need to know how to use the command line for FRC, but it's a useful, if not essential, skill if you want to go beyond.
Practice¶
VS Code is the text editor we will be using to write and run our code, and should have been installed with the WPILib suite during setup. Open up VS Code and follow the "Cloning a repository" section of the VS Code git tutorial to clone this repo.
Navigate to this file in the repo (docs/programming/version-control.md) and add your name to the list below.
People who have added their name
Sebastian Law, Nathan Choi, William Bruce, James Rea, Wesley Tam, Ronit Barman, Sabien Nguyen, Tyler Sheridan, Sabrina Li, Johnathon Zheng, Kenny Xie, Joe Mamma, Hem Dadlani, Cary Yeung, Becky Liu, Ryan Chan, Ray Chang, Jayce Gu, Ian Lin °o°, Kaden Chow ._., Michelle Yeung, Don Huang, Adam Situ, David Li
Now stage and commit your changes with the message add [your name], and then push your changes. Refer to the Git tutorial and VS Code tutorial if needed.
Tip
By convention, commit names are in simple present tense. Things like add name or fix these bugs or update readme.
You are expected to write descriptive commit messages that follow this convention.