Mucha/gitlab branch protection flag #163
Open
+337
−4
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.
Adds --enable-commit-status flag to post a success/failed commit status to
GitLab after scan, enabling merge blocking on Socket findings:
with state, description, and optional report link
MR target project via API
call both methods after scan
merged-results pipelines
graceful error handling
Why?
GitLab users had no way to block MR merges based on Socket scan results.
The CLI exited non-zero on blocking alerts, but that only fails the
pipeline — it doesn't surface a named status check. With
--enable-commit-status, Socket posts a dedicated commit status that repo
admins can require on protected branches, giving explicit merge-gate
control tied to Socket findings without relying solely on pipeline
pass/fail.
Public Changelog
N/A