diff options
| author | Robert Roth <robert.roth.off@gmail.com> | 2018-08-26 23:48:51 +0000 |
|---|---|---|
| committer | Matthias Clasen <mclasen@redhat.com> | 2018-08-26 23:48:51 +0000 |
| commit | 4ed4b4fd6ad5aed3a16934450c09c265a22e89b7 (patch) | |
| tree | d7adb0fb56f3b5e0c305df6072bd191ad0beb2ac /CONTRIBUTING.md | |
| parent | 369cb702e48aaa8b36c963b43399c1bca606d04e (diff) | |
| download | gtk+-4ed4b4fd6ad5aed3a16934450c09c265a22e89b7.tar.gz | |
docs: README.commits converted to markdown
Diffstat (limited to 'CONTRIBUTING.md')
| -rw-r--r-- | CONTRIBUTING.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 318c1ce68e..3326f99043 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -48,9 +48,9 @@ $ ninja ``` **Note**: For information about submitting patches and pushing changes -to Git, see the `README.md` and `README.commits` files. In particular, +to Git, see the [README.md](./README.md) and [README.commits.md](./README.commits.md) files. In particular, don't, under any circumstances, push anything to Git before reading and -understanding `README.commmits`. +understanding [README.commits.md](./README.commits.md). Typically, you should work on your own branch: @@ -60,6 +60,6 @@ $ git checkout -b your-branch Once you've finished working on the bug fix or feature, push the branch to the Git repository and open a new merge request, to let the GTK -maintainers review your contribution. The [CODE-OWNERS](./docs-CODE-OWNERS) +maintainers review your contribution. The [CODE-OWNERS](./docs/CODE-OWNERS) document contains the list of core contributors to GTK and the areas for which they are responsible. |