Skip to content

Latest commit

 

History

History
77 lines (48 loc) · 1.95 KB

workflow.md

File metadata and controls

77 lines (48 loc) · 1.95 KB
Raw

The everyday workflow

The normal everyday workflow in git/github is fairly simple and soon enough should be ingrained in your brain.

flujo

Teamwork via git

One of the possible git distributed workflows is the Integration Manager Workflow.

In this part, we will cover this type of workflow using forks.

###Exercise

  1. Fork this repo.

click it

  1. Clone your fork to your computer

a. Copy the address of the repo (your fork)

click on

b. Go to your terminal or git and write (in the folder where you want your repo)

```git
git clone http_of_your_fork
```
  1. Do 4 and 5 in your local computer.
  2. Add a folder in your fork with your name inside the subdirectory excercises
  3. Add a .txt file with "Hello world! -your name- is commiting to working now with github!"
  4. Go to your terminal and follow your daily workflow
git pull
git add .
git status
git commit -m "I commit to github"
git push
  1. See the changes in your github!

Keeping your fork up to date

  > git remote -v

This command should show only origin pointing to your fork of this tutorial. A remote is a relate repository (with shared history) in which you can do pull or push as you do with your original.

Lets add the remote of this tutorial.

  > git remote add animalito https://github.com/animalito/github_tutorial.git

Execute again git remote -v and you will see 2 repos.

To make pull to the changes that are in remote animalito just do

  > git pull animalito master

Note that to pull from your fork, you still need only do git pull.

Si todo sale bien, ahora pueden hacer push a su fork. Esto mantendrá los cambios sincronizados.