Commit ae7ea511 authored by David Haynes's avatar David Haynes 🙆
Browse files

Merge branch '141-contributing-update' into '2.2-dev'

Slight updates to CONTRIBUTING

See merge request !89
parents 6f46f656 6ef556d4
Pipeline #1283 passed with stage
in 1 minute and 48 seconds
# On Contributing # On Contributing
## git ## git
First take a look at [github flow](https://guides.github.com/introduction/flow/) First take a look at [github flow](https://guides.github.com/introduction/flow/)
as this page gives a good starting point on understanding how to work with `git` as this page gives a good starting point on understanding how to work with `git`
in an open source repo. in an open source repo.
...@@ -77,7 +78,13 @@ Example commit description: ...@@ -77,7 +78,13 @@ Example commit description:
### Merging to the current development branch ### Merging to the current development branch
Once you've finished work in a branch open a [pull request](https://git.gmu.edu/srct/go/merge_requests/new) Once you've finished work in a branch you will need to push your commits to gitlab.
git push origin ##-branchname
`Origin` is gitlab.
Open a [merge request](https://git.gmu.edu/srct/go/merge_requests/new)
to start the process of getting your code into the repo. Your code wil be reviewed to start the process of getting your code into the repo. Your code wil be reviewed
by another member before being merged. Your code must pass our tests and include by another member before being merged. Your code must pass our tests and include
in the description: in the description:
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment