#### Problem There is no unified format for Redis keys names. Without the convention we cannot answer following questions by looking at the key name: 1. Which feature category it belongs to? 2. Where is located the code responsible for the Redis key generation? #### Proposal Update Redis keys to follow the structured name format: ``` <prefix>:<feature_category>:<cache_identifier>:<unique_id> ``` where, * `prefix` - `gl` (for gitlab-rails) * `feature_category` - `source_code_management` ([see the full list](https://gitlab.com/gitlab-org/gitlab/blob/fc51bd13f5bf06b62282a9e466d218f82962963f/config/feature_categories.yml)) * `cache_identifier` - `Repository#branch_names` (class + method where cache is generated) * `unique_id` - `project-1` (any custom identifier necessary for the cache logic) Full example: ``` gl:source_code_management:Repository#branch_names:project-1 ``` See discussion about it in https://gitlab.com/gitlab-org/gitlab/-/issues/378189.