| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
The tarball artifact is in the root directory, but we're exploding it
into the "public" directory.
|
| |
|
|
|
|
|
| |
We want to extract the API reference build to its own template, so we
can share it across projects using gi-docgen.
|
| |
|
|
|
|
|
|
| |
Build json-glib in its own job.
Build the json-glib API reference separately, and then publish it.
|
| |
|
|
|
|
|
| |
Instead of using `ninja` directly, and entering the build directory, we
can use `meson compile`, `meson test`, and `meson dist`.
|
|
|
|
| |
Otherwise `meson dist` will fail.
|
| |
|
|
|
|
|
| |
Otherwise gobject-introspection will fail to build because Python's
distutils are terrible.
|
|
|
|
|
|
|
|
|
| |
Whenever we push a tag, we want to create a distributable archive for
json-glib; this will automate the release process.
Ideally, in the future, we'll have the ability to upload the release
archive straight to download.gnome.org, but for now store the archive
and the generated API reference as CI artefacts.
|
|
|
|
|
|
|
|
|
| |
Improve the CI environment for json-glib:
- build the documentation
- use `meson test` instead of `ninja test`
- store the logs on failure
- do not install the result
|
|
|
|
| |
… And show a fancy badge.
|
|
Only build, run test and install at the moment
|