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
Hide whitespace changes
Inline Side-by-side
Home.md
View page @ cf28df1f
......@@ -24,7 +24,7 @@ Command | Effect
`git config --global core.editor "gedit -w -s" ` | Set commit message editor to `gedit`. Simple GUI editor.
`git config --global core.editor "vim" ` | Set the default commit message editor to `vim`.
### Simple Git flow
### Simple Git Commands
Command | Effect
--- | ---
`git pull` | Fetch the latest code from the GitLab server and update your local copy.
......@@ -34,6 +34,13 @@ Command | Effect
`git commit` | Move the changes from the staging area to `HEAD` on your local machine
`git push` | Send the commits on your local machine to the GitLab server
### Simple Git Flow
1. `git pull`
2. Make changes to your local files in the repo.
2. `git add` files to the staging area.
2. `git commit` the changes in the staging area to a commit.
2. `git push`
## First time using GitLab
This section is aimed towards first time users of both Git and this instance of GitLab.
......@@ -47,10 +54,10 @@ Then from the Wikipedia page about GitLab:
For you, as a student, this means you will
1. Learn how to use version control in order to help prepare you for the working world,
2. Be able to safely submit and track your code, with the over-site of the Lecturers and Demi's,
3. Have a safe place for your project code, provided you push your changes back to the CS GitLab server.
2. Be able to safely submit and track your code, with the over-site of the lecturers and demis,
3. Have a safe place for your project code, provided you push your local changes back to the CS GitLab server.
**NOTE:** Always have a number of backups of your code. GitLab should house one of a few copies of your projects.
**NOTE:** Always have a number of *safe* and *secure* backups of your code. GitLab should house one of a few copies of your projects.
### Login
GitLab has been setup such that you can login with your Stellenbosch University credentials.
......
Clone repository
  • Home