Always regenerate MR cached HTML for selected projects
What does this MR do and why?
Always regenerate MR cached HTML for selected projects
Add a project-scoped, disabled-by-default feature flag (regenerate_merge_request_cached_html) that forces a merge request's title_html/description_html to be treated as stale so they are regenerated and re-persisted on read/write. This lets us observe the cold-cache regeneration path continuously for a selected project.
Staleness is only forced until the first regeneration on an instance to avoid recursing through store_mentions; a freshly loaded record (a new request) regenerates again.
References
Issue - https://gitlab.com/gitlab-org/gitlab/-/work_items/602026+
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
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.