Loading
Remove the rapid_diffs_default_on_mr_show feature flag
What does this MR do and why?
This MR removes the rapid_diffs_default_on_mr_show feature flag, so Rapid Diffs always loads by default on the merge request Changes tab. The flag has been enabled by default on GitLab.com, GitLab Self-Managed, and GitLab Dedicated since 19.4, so nothing changes for users.
The Rapid Diffs toggle stays. Users can still switch to legacy diffs with Switch to classic loading, which stores the choice in the rapid_diffs_enabled cookie. The rapid_diffs_disabled URL param still forces legacy diffs, and rapid_diffs still forces Rapid Diffs. Removing the toggle is out of scope here.
After this MR, administrators on GitLab Self-Managed and GitLab Dedicated can no longer turn Rapid Diffs off for the whole instance by disabling the flag. Each user can still opt out with the toggle. The rollout finished at 100% of actors, and its rollout issue planned this removal.
The specs that only covered the flag-off path are removed, and a spec now covers the rapid_diffs param overriding an opt-out. The docs get a history entry for the removal and drop the [!flag] note, because no feature flag controls Rapid Diffs on the Changes tab any more. Rapid Diffs stays in Beta.
References
- Rollout issue: #609355 (closed)
- Feature issue: #602723 (closed)
- Introduced in: !247629 (merged)
- Removal of
rapid_diffs_on_mr_show: !241051 (merged)
Screenshots or screen recordings
Not applicable. Nothing changes visibly, because the flag is already enabled everywhere.
How to set up and validate locally
- Delete the
rapid_diffs_enabledcookie, then open the Changes tab of any merge request. Rapid Diffs loads. - Select Rapid Diffs > Switch to classic loading. Legacy diffs load, and still load after you reload the page.
- Select Try Rapid Diffs. Rapid Diffs loads again.
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.