Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
First MR in a series updating all redirected links
in CE documentation to the destination URLs
|
|
|
|
For ssot epic
|
|
|
|
|
|
|
|
.gitlab-ci.yml file
|
|
|
|
then each commit or push triggers your CI pipeline.
|
|
The pngquant tool was used https://pngquant.org, and particularly, the
following command:
/usr/bin/pngquant -f --skip-if-larger --ext .png --speed 1 image.png
Before: 47584K
After : 34924K
|
|
|
|
|
|
|
|
[ci skip]
|
|
|
|
|
|
|
|
|
|
|
|
I replaced "merge requests" by "commits". As far as I notice, merge requests per se don't trigger CI; commits and pushes (which are essentially adding commits) do. This is logical: an MR doesn't create anything new, so there is nothing to test.
|
|
[ci skip]
|
|
|
|
Took it from https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/3232
[ci skip]
|
|
The link is now a button under **Pipelines > Pipelines** and **Pipelines > Builds**.
There is no more **CI settings** menu.
|
|
|