forge/pmaports
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions

CI: clarify which commit to put [ci:ignore-count] in (MR 5126)

Browse source 
I've seen confusion about this in the past where people would find it
unclear which commit to put this in.
This commit is contained in:
Stefan Hansson 2024-05-13 16:09:08 +02:00
parent 79b8de8483
commit 6a1f7a1623
No known key found for this signature in database
GPG key ID: 5AE7F5513E0885CB
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
.ci/lib/common.py
View file

@ -148,8 +148,8 @@ a) If you *did not* modify everything listed above, then rebase
branch. Feel free to ask in the chat for help if you need any. branch. Feel free to ask in the chat for help if you need any.
b) If you *did* modify all these packages, and you assume that b) If you *did* modify all these packages, and you assume that
they will build within one hour: skip this sanity check by they will build within one hour: skip this sanity check by
adding '[ci:ignore-count]' to the commit message (then force adding '[ci:ignore-count]' to the commit message of the last
push). commit in the merge request (then force push).
c) If you *did* modify all these packages, and you are sure that c) If you *did* modify all these packages, and you are sure that
they won't build in time, please add '[ci:skip-build]' to the they won't build in time, please add '[ci:skip-build]' to the
commit message (then force push). Make sure that all packages commit message (then force push). Make sure that all packages