Remove alert_message_faq from storage banners
What does this MR do and why?
We noticed that the FAQ link in the storage banners doesn't exist anymore, so we started a discussion in #508743 (comment 2283645097) on how to proceed.
PM and TW decided that we should remove the paragraph related to the FAQ and link the mention of "storage" in the copy to the Storage Usage Quotas docs
References
Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Project Repository Limis
| Storage Status | Before | After |
|---|---|---|
| Over limit; no purchased storage | ![]() |
![]() |
| Approaching purchased storage limit | ![]() |
![]() |
| Over purchased storage limit | ![]() |
![]() |
Namespace Limis
| Storage Status | Before | After |
|---|---|---|
| Approaching limit; no purchased storage | ![]() |
![]() |
| Over limit; no purchased storage | ![]() |
![]() |
| Approaching purchased storage limit | ![]() |
![]() |
| Over purchased storage limit | ![]() |
![]() |
How to set up and validate locally
- Prerequisites
- Simulate SaaS GitLab.com
- Enable these setting in
rails console:Gitlab::CurrentSettings.update!(automatic_purchased_storage_allocation: true)Gitlab::CurrentSettings.update!(repository_size_limit: 10.gigabytes)Gitlab::CurrentSettings.update!(enforce_namespace_storage_limit: true)
Project Repository Limits
- Create or choose a group to work on. Make note of its id, e.g.:
147/group = Group.find(147) - Create 2 projects under this group. Make note of its ids, e.g.:
45and46 - Now add some storage to the projects
Project.find(45).statistics.update(repository_size: 14.gigabytes)Project.find(46).statistics.update(repository_size: 8.gigabytes)
- Propagate this data to the group:
Sidekiq.redis(&:flushdb)Namespaces::ScheduleAggregationWorker.perform_sync(g.id)Namespaces::RootStatisticsWorker.perform_sync(g.id)
- To add purchased storage, use group.update(additional_purchased_storage_size: 10*1024)
- Keep changing the data and compare the screenshots
Namespace Limits
- Enable these setting in
rails console:Plan.free.actual_limits.update!(notification_limit: 5*1024)Plan.free.actual_limits.update!(enforcement_limit: 5*1024)Plan.free.actual_limits.update!(storage_size_limit: 5*1024)::Feature.enable(:namespace_storage_limit)
- Create or choose a group to work on. Make note of its id, e.g.:
147/group = Group.find(147) - Create 2 projects under this group. Make note of its ids, e.g.:
45and46 - Now add some storage to the projects
Project.find(45).statistics.update(repository_size: 14.gigabytes)Project.find(46).statistics.update(repository_size: 8.gigabytes)
- Propagate this data to the group:
Sidekiq.redis(&:flushdb)Namespaces::ScheduleAggregationWorker.perform_sync(g.id)Namespaces::RootStatisticsWorker.perform_sync(g.id)
- To add purchased storage, use group.update(additional_purchased_storage_size: 10*1024)
- Keep changing the data and compare the screenshots
Edited by Sheldon Led













