Verified Solution

[gitlab-org/gitlab] [FF] Rollout read_project_push_rules, and write_project_push_rules feature flags on self-managed

Sponsored Content
### ROOT CAUSE The feature is currently gated by two feature flags (`read_project_push_rules` and `write_project_push_rules`), preventing it from being enabled by default. To roll it out, the flags must be set to `true` to enable the feature. ### CODE FIX To enable the feature, set the feature flags to `true` in the production environment. This can be done via chatops or by directly updating the database. Here are the steps: 1. **Using Chatops** (recommended for self-managed GitLab): ```bash # Set the read_project_push_rules flag to true gitlabctl flags set read_project_push_rules true # Set the write_project_push_rules flag to true gitlabctl flags set write_project_push_rules true ``` 2. **Direct Database Update** (if chatops is not available): - Connect to the production database. - Update the `feature_flags` table: ```sql UPDATE feature_flags SET value = 'true' WHERE name = 'read_project_push_rules'; UPDATE feature_flags SET value = 'true' WHERE name = 'write_project_push_rules'; ``` 3. **Verify the Flags**: ```bash gitlabctl flags list ``` This will enable the feature for all users in the production environment. Monitor dashboards like `GitLab's CI/CD pipeline success rates` and `Incident Management` for any issues post-rollout.
Deploy on DigitalOcean ($200 Credit)

Related Fixes

[rust-lang/rust] Cranelift patch files are painful to maintain
[golang/go] x/tools/gopls/internal/test/integration/misc: TestDeprecated70736/default failures
[docker/cli] Deprecated project ScatterHQ/Flocker given as example in docs/extend/plugins_volume.md