[go: up one dir, main page]

Skip to content

Introduce project level setting to toggle rename following for file history page

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

By default, the GitLab file commit history page follows file renames to provide a more complete history of the file. For very large repositories with deep commits, performing rename detection on a file can take a significant amount of time and lead to a sluggish user experience. See gitaly#5821 (closed).

As a temporary workaround to mitigate this issue, !144263 (merged) introduces a feature flag that can disable the rename detection done on the file commit history page instance-wide when enabled. While this solution fixes the problem it is not ideal because it is currently implemented as a feature flag and disables rename detection for all projects not just the large ones that need it.

Instead, we should introduce a project level setting to toggle rename following on the file commit history page. This will give better flexibility and control over each project and alleviate the sluggish user experience. Maybe this setting could be part of a "monorepo" settings section 🤔

Related: gitaly#5821 (closed)

/cc @mcbabin @andrashorvath

Edited by 🤖 GitLab Bot 🤖