docs: Mark [ci:ignore-count] as removed

Keeping it in the docs under a new section to reduce the risk of
confusion about its disappearance. It's also still relevant if you
target older branches where it hasn't been removed.

Signed-off-by: Stefan Hansson <newbyte@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7822>
This commit is contained in:
Stefan Hansson 2026-01-23 13:11:17 +01:00 committed by The Friendly Merge Bot
parent e331eb74f8
commit ffbce2d731
No known key found for this signature in database

View file

@ -1,13 +1,13 @@
# CI tags
You can add various tags in the commit message of your last commit to modify
the continuous integration behaviour for your merge requests:
the continuous integration behaviour for your merge requests.
## Current CI tags
* `[ci:skip-build]`: Do not build modified packages, only verify their
checksums. Use this when pushing changes to an MR that should not trigger a
complete build.
* `[ci:ignore-count]`: Allow skipping the "too many packages changed" check.
Use this when automatically modifying many device packages.
* `[ci:skip-vercheck]`: Do not verify if the version of a changed package has
been increased. Use this, when making a cosmetic change in an APKBUILD that
should not cause the package to get rebuilt, or when changing the enabled
@ -23,3 +23,11 @@ the continuous integration behaviour for your merge requests:
GitLab [feature](https://docs.gitlab.com/ci/pipelines/#skip-a-pipeline). Use
this only in very extreme situations where CI might be broken, but a change is
needed to fix critical bugs. Whenever possible, try to use the other tags.
## Former CI tags
* `[ci:ignore-count]`: Allow skipping the "too many packages changed" check.
Use this when automatically modifying many device packages.
* Removed after v25.12 together with the package count check as it hampered
productivity to little gain since we no longer have runners with limited
compute minutes.