Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • Git Beginners Git Beginners
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Computer-ScienceComputer-Science
  • Git BeginnersGit Beginners
  • Wiki
  • Home

Home · Changes

Page history
Update Home authored Jul 20, 2018 by Andrew James Collett's avatar Andrew James Collett
Show whitespace changes
Inline Side-by-side
Home.md
View page @ 122939ba
...@@ -29,8 +29,9 @@ Command | Effect ...@@ -29,8 +29,9 @@ Command | Effect
--- | --- --- | ---
`git pull` | Fetch the latest code from the GitLab server and update your local copy. `git pull` | Fetch the latest code from the GitLab server and update your local copy.
`git status` | Show the current status of the local working tree. `git status` | Show the current status of the local working tree.
`git add <file or folder>` | `git diff <file or folder>` | Show changes from the file or all files if none specified.
`git commit` | `git add <file or folder>` | Add the specific file or folder to the index.
`git commit` | Move
`git push` | `git push` |
...@@ -75,9 +76,13 @@ Next, we will need to add your SSH key so that you can `clone` a copy of the pro ...@@ -75,9 +76,13 @@ Next, we will need to add your SSH key so that you can `clone` a copy of the pro
All commands need to be executed within the directory of your git repo. All commands need to be executed within the directory of your git repo.
### Best practices for your own (and others) sanity ### Best practices for your own (and others) sanity
1. Add changes to your commit often 1. Add changes to your commit often.
2. Commit when-ever you step away from your work. 2. Commit when-ever you step away from your work.
3. Try keep all changes in a commit related. The above is more important than this though. 3. Try keep all changes in a commit related. The above is more important than this though.
4. Make your commit messages helpful. Short, but descriptive. Remember you can enter a 2nd line of text. 4. Make your commit messages helpful. Short, but descriptive. Remember you can enter a 2nd line of text.
### Links and Videos ### Links and Videos
Link | Description
--- | ---
[git - the simple guide](http://rogerdudler.github.io/git-guide/) | A short but decent guide. Helpful if you want to setup on your own PC.
\ No newline at end of file
Clone repository
  • Home