Week 0 Notes
Popular in Advanced Programming
verified elite notetaker
Popular in Department
This 2 page Class Notes was uploaded by bloodiris0312 on Friday September 23, 2016. The Class Notes belongs to PIC10C at University of California - Los Angeles taught by Ricardo Salazar in Fall 2016. Since its upload, it has received 4 views.
Reviews for Week 0 Notes
Report this Material
What is Karma?
Karma is the currency of StudySoup.
You can buy or earn more Karma at anytime and redeem it for class notes, study guides, flashcards, and more!
Date Created: 09/23/16
PIC10C Week 0 23.09 L Version Control - Git (GitHub) *Big C++ book unnecessary There will be no new information other than more advanced features, such as Qt. Final project is a 6-week project that will be self-defined and set at Week 2 or 3. Git Learn how to use Git at Try Git Every command begins with git. Commands used in the tutorial above listed below: init initializes a repository status prints the current state of the project add … adds … to the staging area. Staged files can be committed to the project. Untracked files are usually newly created files. remote add … --- adds remote repository named … with URL --- Main repository typically called origin reset … removes … from the staging area. commit -m …adds message … ‘*.txt’ wildcard that adds all files with the ending .txt Wildcard formula: ‘ … ‘ log provides a summary of all changes log --summary a more specific version of log push … --- pushes commits to remote … , branch --- Default local branch is master -u … remember … (repository location to push to) pull … --- pulls new changes to remote … , branch --- diff finds all changes from your last commit HEAD pointer pointing to your most recent commit diff --staged changes in the staging area checkout --… undoes all actions after the last commit for file … Suggested public repository location: GitHub Private repository location: Atlassian (up to 5 collaborators) Branches Master branch: original code. If there is a product and it’s running, the running version would be the master branch. Other branches can be made to test other features without breaking the original code. Merging with master branch is possible. Patches that are not pushed to the public yet are other branches. When they are published, the patches are merged with the master branch. branch … moves to branch … , or creates it branch -d … deletes branch with name … checkout … switches to branch … rm … removes … merge … merges … with current branch push pushes everything up to now onto the remote repository
Are you sure you want to buy this material for
You're already Subscribed!
Looks like you've already subscribed to StudySoup, you won't need to purchase another subscription to get this material. To access this material simply click 'View Full Document'