[go: up one dir, main page]

Skip to content

[Draft] Add alerts for repository mirroring

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

Context !174976 (comment 2254822144) | #372200 (closed)

Proposal: Initial Iteration

Currently, when a repository is being mirrored, users see a block of text on the Project overview page but nowhere else in Code. It would be useful to add this alert to the Repository page as well, and communicate this in a scalable way.

Due to feedback below, we are re-approaching this design proposal and will add a new proposal when the time is appropriate.

Current Proposed

Project overview page

Mirroring

Screenshot 2024-12-13 at 10.49.46 PM.png

Mirroring + read-only repository

Screenshot 2024-12-13 at 10.53.16 PM.png

Mirroring error

error.png

Mirroring error with pause

error2.png

Project overview page

Mirroring

Alert - Project landing - mirror.jpg

Mirroring + read-only repository

Alert - Project landing - mirror readonly.jpg

Mirroring error

Alert - Repository - mirror error.jpg

Mirroring error with pause

Alert - Repository - mirror error 2.jpg

Repository page

Mirroring

Screenshot 2024-12-13 at 10.49.46 PM.png

Mirroring + read-only repository

Mirroring error

Mirroring error with pause

Screenshot 2024-12-13 at 10.51.53 PM.png

Repository page

Mirroring

Alert - Repository - mirror.jpg

Mirroring + read-only repository

Alert - Repository - mirror readonly.jpg

Mirroring error

Alert - Repository - mirror error.jpg

Mirroring error with pause

Alert - Repository - mirror error 2.jpg

Settings page

Mirroring

Screenshot 2024-12-13 at 10.48.06 PM.png

Mirroring + read-only repository

Screenshot 2024-12-13 at 10.48.06 PM.png

Settings page

Mirroring (no change)

settings-production.png

Mirroring + read-only repository

Current_ Branch rules overview.jpg

Mirroring error

Alert - Repository Settings - mirror error.jpg

Mirroring error with pause

Alert - Repository Settings - mirror error 2.jpg

Design Feedback

  • #509463 (comment 2266620578)
  • Alerts should be reserved for information that users really need to know in that task/instance, and take up a large amount of screen real estate at the top
  • Yellow/red alerts make sense because users need to be aware of errors
  • Forks experience similar issues, in that many community contributors fork repositories but have a difficult time telling apart forked repositories from upstream repositories

Next Steps

  • @alyssatrinh will have to re-approach the design to incorporate this feedback, and also find an elegant solution that works for mirrors and forks
  • We will still use the alerts for error states, but they may be scaled down
Edited by 🤖 GitLab Bot 🤖