Design Repo Sync Status - Actions
-
Filtering MR must be merged first (target branch) - !19589 (merged)
Important Notes
This MR was originally created in !19116 (closed). This is an effort to split that work into 3 separate MRs. This one being the third and final.\
The first MR !19588 (closed) got to be too big. This MR is an effort to split that first MR into two. A lot of the feedback related to this change can be found there.
!19588 (closed) split:
MR that also must go first:
Closes #34336 (closed)
What does this MR do?
This adds the ability for users to force resync a design repository or all design repositories.
Describe in detail what your merge request does and why.
This MR adds the ability to take action against a Design Repository in regards to its Geo sync status.
Users will be able to click to Resync a particular Design Repository, or use a Batch action and resync them all.
Screenshots
GIF of single Action and Batch Action
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
cc: @ekigbo