fix(safe-settings): allow GitLab CI to bypass status checks for releasing#110
Merged
dafyddj merged 1 commit intosaltstack-formulas:masterfrom Mar 16, 2026
Merged
Conversation
5483058 to
bd5ee60
Compare
…sing * Releases are currently managed using GitLab CI so GitHub doesn't know whether the status checks have passed or not (on GitLab). This bypass allows `semantic-release` to push to the `master` branch using the `saltstack-formulas-github` user token.
bd5ee60 to
8e19413
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
whether the status checks have passed or not (on GitLab).
This bypass allows
semantic-releaseto push to themasterbranchusing the
saltstack-formulas-githubuser token.