We have already set up a remote called “staff” that points to our skeleton code repos on GitHub, for both your personal and group repo. The Git Remotes feature allows you to link GitHub repositories to your local Git repository. Communication with course staff will often involve looking at the code and commits in your repo. Breaking up the implementation of a large feature into several, small, clear commits is good practice, and will make it easier to determine where in your codebases’ history a bug was introduced. Back them up by pushing to your GitHub repo. Your working files will be stored within the VM. You will use the “Remotes” feature of Git to pull code from our skeleton repos (when we release new skeleton code) and push code to your personal and group repos (when you submit code). These two skeleton code repositories are already checked out in the home folder of your VM, inside ~/code/personal and ~/code/group. We will publish skeleton code for homeworks in Berkeley-CS162/student0 and we will publish skeleton code for group projects in Berkeley-CS162/group0.
You will have access to two private repositories in this course: a personal repository for homework, and a group repository for projects.
Alternatively, you can use the instructions in the previous “New GitHub Users” section. Then, you can still use vagrant ssh to SSH into your machine. You can enable SSH agent forwarding in your Vagrantfile by enabling _agent = true. If you already have a GitHub SSH keypair set up on your local machine, you can use your local ssh-agent to utilize your local credentials within the virtual machine via SSH agent forwarding. The key should start with “ssh-rsa” and end with Experienced GitHub users The title of your SSH keypair can be “CS 162 VM”. You should log in to GitHub and go to /settings/ssh to add this SSH public key to your GitHub account. The second command displayed the public key on your screen. The first command created a new SSH keypair.
0 kommentar(er)
