Step 1 - Create Feature Flag for reject_unsigned_commits_by_gitlab [RUN ALL RSPEC] [RUN AS-IF-FOSS]
- Step 1 - Create Feature Flag for reject_unsigned_commits_by_gitlab
- Step 2 - Add docs for "Reject unsigned commits" caveats
What does this MR do?
This MR wraps some behavior we introduced in !54166 (merged) around a feature flag. This way local instance admins can toggle this temporary behavior off while we work on the holistic solution #19185 (closed).
Screenshots (strongly suggested)
With a project that has the Reject unsigned commits
push rule:
Feature flag DEFAULT/ON | Feature flag OFF |
---|---|
![]() |
![]() |
You'll notice that the new feature flag is defaulted to ON.
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have not included a changelog entry because "No user facing changes".
-
-
Documentation in follow-up !58465 (merged) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Related to #326023 (closed)
Edited by Paul Slaughter