You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If split up, I can use the tag commit (without skip-ci) for further processing and releasing of the tag packages, DEBs, and/or JARs in CI. So I have to use --disable-final-skip-ci and find a way around the automated main commit to NOT start another build.
Any ideas?
The text was updated successfully, but these errors were encountered:
...doing --disable-final-skip-ci now and react with CI to the tag, main commit and push will be ruled out by a Gitlab CI rule looking at the version number in the commit, such as if: $CI_COMMIT_REF_NAME == "main" && $CI_COMMIT_TITLE !~ /^[\d\.]+$/
If split up, I can use the tag commit (without skip-ci) for further processing and releasing of the tag packages, DEBs, and/or JARs in CI. So I have to use --disable-final-skip-ci and find a way around the automated main commit to NOT start another build.
Any ideas?
The text was updated successfully, but these errors were encountered: