Commit 6e433b19 authored by Ben Boeckel's avatar Ben Boeckel

CONTRIBUTING: use plain git push

The gitlab-push script is no longer used.
parent 49fc2c9d
......@@ -136,7 +136,7 @@ Typically, one addresses issues by writing code. To start contributing to SMTK:
7. Push commits in your topic branch to your fork in GitLab:
$ git gitlab-push
$ git push gitlab HEAD
For more information see: [Share a Topic][]
......
......@@ -81,8 +81,8 @@ Update
2. Optionally push `master` to your fork in GitLab:
$ git push gitlab master
to keep it in sync. The `git gitlab-push` script used to
[Share a Topic](#share-a-topic) below will also do this.
to keep it in sync.
Create a Topic
--------------
......@@ -145,13 +145,11 @@ signed in for [GitLab Access][] and created your fork by visiting the main
3. Push commits in your topic branch to your fork in GitLab:
$ git gitlab-push
$ git push gitlab HEAD
Notes:
* If you are revising a previously pushed topic and have rewritten the
topic history, add `-f` or `--force` to overwrite the destination.
* The `gitlab-push` script also pushes the `master` branch to your
fork in GitLab to keep it in sync with the upstream `master`.
The output will include a link to the topic branch in your fork in GitLab
and a link to a page for creating a Merge Request.
......
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