luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-08-02 07:23:41 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs: Mention how to run the test suite in CONTRIBUTING.md

Browse Source 
We don’t want `CONTRIBUTING.md` to become an exhaustive manual of how to
contribute to what is a fairly standard C project using Meson, but it is
a fairly helpful hint to mention how to run the test suite. Then people
can use `meson test --help` and the Meson documentation to learn more.

Pointed out on !4589.

Signed-off-by: Philip Withnall <pwithnall@gnome.org>
This commit is contained in:
Philip Withnall
2025-04-12 18:32:09 +01:00
parent 841b565b8d
commit c077153699
1 changed files with 9 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
CONTRIBUTING.md
View File

@@ -153,7 +153,15 @@ Typically, you should work on your own branch:
$ git checkout -b your-branch
```
Once you’ve finished working on the bug fix or feature, push the branch
Once you’ve finished working on the bug fix or feature, make sure the tests
pass by using the standard `meson` test harness:
```sh
$ meson test -C _builddir
$ meson test -C _builddir --setup=valgrind
```
Then push the branch
to the Git repository and open a new merge request, to let the GLib
core developers review your contribution.