- 11 Mar:
- If you are not familiar with github and how it works. Check this excellent video tutorial by Daniel Shiffman.
- https://www.youtube.com/watch?v=BCQHnlnPusY&list=PLRqwX-V7Uu6ZF9C0YMKuns9sLDzK6zoiV
- Here are few useful tips I found when using terminal git:
- It's cool and let you show off more compared to using github desktop/web github.
- If you are not sure about any command always use 'git help' for information.
- Always start with 'git pull'.
- To discard your uncommited changes and rollback to when you pull. Use 'git checkout .' WARNING: Your work will lost after this command.
- There will be distinct section for each problem sets, please commit your file to the corresponding directory
- The formatting of directory will be:
- Directory: Great Genre of the problem (E.g. UVaProblem, Lab)
- Directory: Sub Genre, id of the question/workshop (E.g. p14, Lab1)
- File: question specification, for others to reference. Best to be pdf format.
- Directory: Your Id, for identifying the author, This can be annoymous or can be your real name.
- Your program. (E.g. Prog.c) Note: Executable File will be excluded by .gitignore
- Directory: Sub Genre, id of the question/workshop (E.g. p14, Lab1)
- So full example: UVaQuestions/p14/xxxx/prog.c(also test cases/Outputs)
- Directory: Great Genre of the problem (E.g. UVaProblem, Lab)
- To be added when Gabe announced Half-life 3
- Always add comment to commits so that others know what you did.
- Add comments to your program if possible
- If you spot bug(i.e. feature), or suggest changes to others' programs. Use 'Issues' tab to discuss the problem. Which is located above, near the code tab. Do NOT change other's program directly.
- Happy collaboration