Profile page: Increase spacing after profile avatar
What does this MR do and why?
Profile page: Increase spacing after profile avatar
Increases the spacing between the profile avatar and the following content. Especially a problem if a user sets themself as busy.
Reported by @lohrc in #431615 (comment 1783907847)
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
Before | After |
---|---|
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
How to set up and validate locally
Set a profile to «Busy»
- Go to http://gdk.test:3000/-/user_settings/profile
- Enable «Set yourself as busy»
- Save
Check pages
Related to #424397 (closed), #431615 (closed)
Merge request reports
Activity
changed milestone to %16.10
assigned to @seggenberger
mentioned in issue #431615 (closed)
- A deleted user
added backend label
1 Warning You've made some app changes, but didn't add any tests.
That's OK as long as you're refactoring existing code,
but please consider adding any of the maintenancepipelines, maintenancerefactor, maintenanceworkflow, documentation, QA labels.Reviewer roulette
Category Reviewer Maintainer backend @j_lar
(UTC+1, same timezone as author)
@mwoolf
(UTC+0, 1 hour behind author)
frontend @rhardarson
(UTC+1, same timezone as author)
@sdejonge
(UTC+11, 10 hours ahead of author)
UX @timnoah
(UTC+0, 1 hour behind author)
Maintainer review is optional for UX Please check reviewer's status!
Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger- Resolved by Scott de Jonge
removed review request for @jmiocene
- Resolved by Scott de Jonge
@jmiocene
, thanks for approving this merge request.This is the first time the merge request has been approved. To ensure we don't only run predictive pipelines, and we don't break
master
, a new pipeline will be started shortly.Please wait for the pipeline to start before resolving this discussion and set auto-merge for the new pipeline. See merging a merge request for more details.
added pipeline:mr-approved label
E2E Test Result Summary
allure-report-publisher
generated test report!e2e-test-on-gdk:
test report for 2528c9a7expand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Verify | 36 | 0 | 0 | 0 | 36 | ✅ | | Create | 60 | 0 | 9 | 0 | 69 | ✅ | | Data Stores | 31 | 0 | 0 | 0 | 31 | ✅ | | Plan | 53 | 0 | 0 | 0 | 53 | ✅ | | Package | 24 | 0 | 2 | 0 | 26 | ✅ | | Govern | 66 | 0 | 0 | 0 | 66 | ✅ | | Monitor | 7 | 0 | 0 | 0 | 7 | ✅ | | Manage | 0 | 0 | 1 | 0 | 1 | ➖ | | Release | 5 | 0 | 0 | 0 | 5 | ✅ | | Analytics | 2 | 0 | 0 | 0 | 2 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 284 | 0 | 12 | 0 | 296 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+
@sdejonge, did you forget to run a pipeline before you merged this work? Based on our code review process, if the latest pipeline was created more than 4 hours ago, you should:
- Ensure the merge request is not in Draft status.
- Start a pipeline (especially important for Community contribution merge requests).
- Set the merge request to auto-merge.
This is a guideline, not a rule. Please consider replying to this comment for transparency.
This message was generated automatically. You're welcome to improve it.
mentioned in commit 95073a01