| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
For ci-fairy check-commits to pick it up. These are mostly cosmetic:
- Require that the commit subject has a prefix
- Prevent commits from having links to the merge request itself
(should be already there via merge commits)
- Ensure commit subjects are properly capitalized
- Avoid code filenames in commit subject
We could add some further things in the future, like enforcing a
set of prefixes to use in commit log subjects.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
It is somewhat easy to dismiss failed build images as errors in
the pipeline rather than errors in the repository configuration.
Make a separate check in the review stage testing that the user
repository is in a state able to run the rest of CI (e.g. generating
or storing images in its own container registry, since this is
necessary with ci-templates).
The error message is made known through both junit and CI job output.
|
| |
|
|
|
| |
For the "pages" stage we need docs and manpages from both projects,
use a shallow clone of tracker-miners for the purpose.
|
|
|
Run `mkdocs` in the toplevel directory to generate the HTML.
The last time Tracker had a website was 2011
(http://web.archive.org/web/20110307070049/http://projects.gnome.org/tracker)
so this is very exciting.
The website is published here:
https://gnome.pages.gitlab.gnome.org/tracker/
The latest API reference documentation is built and included in the
Tracker website, available under the /docs/api-preview/ prefix.
This allows us to browse and reference the documentation during
Tracker 3.0 development, as well as providing a sort of work around
for https://gitlab.gnome.org/GNOME/tracker/-/issues/100.
A warning is added to each documentation page advising that it is
a preview built from Git.
|
