Default enable repository_lock_information feature flag

Chaoyue Zhaorequested to merge
619410-default-enable-repository-lock-information into master

What does this MR do and why?

Moves the repository_lock_information flag from gitlab_com_derisk to beta and sets default_enabled: true. The gitlab_com_derisk type does not support default_enabled: true, so converting to beta is the documented path for releasing a flag while retaining it as a kill switch. This makes the improved file and directory lock UX — lock information and lock/unlock buttons on repository file and tree pages — available by default on self-managed and GitLab Dedicated instances, not only on GitLab.com.

The flag has been fully enabled on GitLab.com since 2026-09-02 with no regressions reported.

References

Screenshots or screen recordings

No new UI is introduced by this MR. It only changes the default state of an existing flag; the visual change to file lock behavior was shipped in 19.4 behind this flag.

How to set up and validate locally

  1. Start a GDK instance with a valid GitLab Premium or Ultimate license (file locking is an EE feature).

  2. Open a Rails console (gdk rails console).

  3. Confirm the flag is enabled by default without any explicit override:

    project = Project.find_by_full_path('your-test-group/your-test-project')
Feature.enabled?(:repository_lock_information, project)
# => true

  4. Visit a repository file page (for example http://gdk.test:3000/your-test-group/your-test-project/-/blob/main/README.md) and a directory page for that project. Confirm that lock information and the lock/unlock buttons are visible for users with at least the Developer role.

  5. Disable the flag and confirm the old behavior is restored:

    Feature.disable(:repository_lock_information)

    Reload the file and directory pages — the new lock UI should no longer appear.

  6. Re-enable the flag to leave your environment in the default state:

    Feature.enable(:repository_lock_information)

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports