Refactor: user profile page to Vue

changed the description

Thank you for your contribution to GitLab. Please refer to the contribution documentation for an overview of the process.

When you're ready for a first review, post @gitlab-bot ready. If you know a relevant reviewer(s) (for example, someone that was involved in a related issue), you can also assign them directly with @gitlab-bot ready @user1 @user2.

At any time, if you need help, feel free to post @gitlab-bot help or initiate a mentor session on Discord. Read more on how to get help.

You can comment @gitlab-bot label <label1> <label2> to add labels to your MR. Please see the list of allowed labels in the label command documentation.

This message was generated automatically. You're welcome to improve it.

added Community contribution workflowin dev labels

assigned to @JeremyWuuuuu

added 1 commit

013ab0bd - Refactor: user profile page to Vue

Compare with previous version

Hey @JeremyWuuuuu!

Thank you for your contribution to GitLab. Please refer to the contribution documentation for an overview of the process.

When you're ready for a first review, post @gitlab-bot ready. If you know a relevant reviewer(s) (for example, someone that was involved in a related issue), you can also assign them directly with @gitlab-bot ready @user1 @user2.

At any time, if you need help, feel free to post @gitlab-bot help or initiate a mentor session on Discord. Read more on how to get help.

You can comment @gitlab-bot label <label1> <label2> to add labels to your MR. Please see the list of allowed labels in the label command documentation.

This message was generated automatically. You're welcome to improve it.

added linked-issue label

2 Warnings

featureaddition and featureenhancement merge requests normally have a documentation change. Consider adding a documentation update or confirming the documentation plan with the Technical Writer counterpart.

For more information, see:

The Handbook page on merge request types.
The definition of done documentation.

This merge request does not refer to an existing milestone.

Reviewer roulette

Changes that require review have been detected!

Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:

Category	Reviewer	Maintainer
backend	Eulyeon K. (`@euko`) (UTC+9)	Mikołaj Wawrzyniak (`@mikolaj_wawrzyniak`) (UTC+0)
frontend	Nataliia Radina (`@nradina`) (UTC+2)	Paul Gascou-Vaillancourt (`@pgascouvaillancourt`) (UTC-4)
test for `spec/features/*`	Eulyeon K. (`@euko`) (UTC+9)	Maintainer review is optional for test for `spec/features/*`

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

LGTM

@gitlab-bot ready @peterhegman

marked this merge request as ready

added workflowready for review label and removed workflowin dev label

requested review from @peterhegman

@peterhegman, this Community contribution is ready for review.

Do you have capacity and domain expertise to review this? We are mindful of your time, so if you are not able to take this on, please re-assign to one or more other reviewers.
Add the workflowin dev label if the merge request needs action from the author.

This message was generated automatically. You're welcome to improve it.

added backend feature flag featureaddition frontend grouptenant scale typefeature labels

2 Warnings

featureaddition and featureenhancement merge requests normally have a documentation change. Consider adding a documentation update or confirming the documentation plan with the Technical Writer counterpart.

For more information, see:

The Handbook page on merge request types.
The definition of done documentation.

This merge request does not refer to an existing milestone.

Reviewer roulette

Changes that require review have been detected!

Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:

Category	Reviewer	Maintainer
backend	Alex Buijs (`@alexbuijs`) (UTC+2)	Igor Drozdov (`@igor.drozdov`) (UTC+2)
frontend	Mireya Andres (`@mgandres`) (UTC+8)	Justin Ho (`@justin_ho`) (UTC+7)
test for `spec/features/*`	Alex Buijs (`@alexbuijs`) (UTC+2)	Maintainer review is optional for test for `spec/features/*`

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

added devopsdata stores sectioncore platform labels

mentioned in commit gitlab-org-sandbox/gitlab-jh-validation@789f6e7f

Allure report

allure-report-publisher generated test report!

e2e-test-on-gdk: test report for fe36c432

expand test summary

+-----------------------------------------------------------------------+
|                            suites summary                             |
+------------------+--------+--------+---------+-------+-------+--------+
|                  | passed | failed | skipped | flaky | total | result |
+------------------+--------+--------+---------+-------+-------+--------+
| Create           | 8      | 0      | 1       | 0     | 9     | ✅     |
| Plan             | 4      | 0      | 0       | 0     | 4     | ✅     |
| Manage           | 1      | 0      | 0       | 0     | 1     | ✅     |
| Monitor          | 4      | 0      | 0       | 0     | 4     | ✅     |
| Govern           | 2      | 0      | 0       | 0     | 2     | ✅     |
| Data Stores      | 2      | 0      | 0       | 1     | 2     | ❗     |
| Framework sanity | 0      | 0      | 1       | 0     | 1     | ➖     |
+------------------+--------+--------+---------+-------+-------+--------+
| Total            | 21     | 0      | 2       | 1     | 23    | ❗     |
+------------------+--------+--------+---------+-------+-------+--------+

e2e-package-and-test: test report for fe36c432

expand test summary

+------------------------------------------------------------+
|                       suites summary                       |
+-------+--------+--------+---------+-------+-------+--------+
|       | passed | failed | skipped | flaky | total | result |
+-------+--------+--------+---------+-------+-------+--------+
+-------+--------+--------+---------+-------+-------+--------+
| Total | 0      | 0      | 0       | 0     | 0     | ➖     |
+-------+--------+--------+---------+-------+-------+--------+

e2e-review-qa: test report for fe36c432

expand test summary

+-----------------------------------------------------------------------+
|                            suites summary                             |
+------------------+--------+--------+---------+-------+-------+--------+
|                  | passed | failed | skipped | flaky | total | result |
+------------------+--------+--------+---------+-------+-------+--------+
| Manage           | 1      | 0      | 0       | 0     | 1     | ✅     |
| Create           | 8      | 0      | 1       | 0     | 9     | ✅     |
| Monitor          | 4      | 0      | 0       | 0     | 4     | ✅     |
| Data Stores      | 2      | 0      | 0       | 1     | 2     | ❗     |
| Govern           | 2      | 0      | 0       | 0     | 2     | ✅     |
| Plan             | 3      | 0      | 1       | 0     | 4     | ✅     |
| Framework sanity | 0      | 0      | 1       | 0     | 1     | ➖     |
+------------------+--------+--------+---------+-------+-------+--------+
| Total            | 20     | 0      | 3       | 1     | 23    | ❗     |
+------------------+--------+--------+---------+-------+-------+--------+

added 407 commits

013ab0bd...4f3225e5 - 405 commits from branch gitlab-org:master
f8a7ceec - Refactor: user profile page to Vue
0182cab9 - Test: stub the newly added FF for testing

Compare with previous version

added 1 commit

b07e5c16 - Revert changes in strcuture.sql

Compare with previous version

added 1 commit

ce918d5a - Revert changes in strcuture.sql

Compare with previous version

added 1 commit

06a5cd77 - Move FF stub to the start of the before action

Compare with previous version

added 1 commit

544e6219 - Feat: add an empty Vue component for mounting

Compare with previous version

removed review request for @peterhegman

Hi @peterhegman

We noticed this MR is marked as workflowready for review but no reviewer is assigned. workflowin dev has automatically been applied to this MR based on the likelihood the review is finished. If additional reviews are still required, please assign a reviewer and reapply workflowready for review.

@JeremyWuuuuu you may also request a review by commenting @gitlab-bot ready. You can also assign reviewers directly using @gitlab-bot ready @user1 @user2 if you know the relevant reviewer(s), such as those who were involved in a related issue.

This message was generated automatically. You're welcome to improve it.

added workflowin dev label and removed workflowready for review label

mentioned in issue gitlab-jh/status-reports#232

@gitlab-bot ready @peterhegman

added workflowready for review label and removed workflowin dev label

requested review from @peterhegman

@peterhegman, this Community contribution is ready for review.

Do you have capacity and domain expertise to review this? We are mindful of your time, so if you are not able to take this on, please re-assign to one or more other reviewers.
Add the workflowin dev label if the merge request needs action from the author.

This message was generated automatically. You're welcome to improve it.

Hi @peterhegman, I have addressed the comments you left, and created the rollout issue at rollout_issue_url: #414552, would you mind taking a look at it for me? Thanks in advance!

added 1 commit

2a797efc - Rename feature flag and address MR comments

Compare with previous version

added 664 commits

2a797efc...2ee3031d - 658 commits from branch gitlab-org:master
298e1fac - Refactor: user profile page to Vue
8e8fb4a6 - Test: stub the newly added FF for testing
c65f6b17 - Revert changes in strcuture.sql
e5c865fc - Move FF stub to the start of the before action
f0469647 - Feat: add an empty Vue component for mounting
b08ba785 - Rename feature flag and address MR comments

Compare with previous version

Note to future reviewers: There are a lot of whitespace changes in this MR because we added a feature flag and had to indent a large block of code. If you turn off the Show whitespace changes setting in the upper right corner of the diff view it is much easier to review.

approved this merge request

requested review from @jivanvl and @alexbuijs and removed review request for @peterhegman

@peterhegman, thanks for approving this merge request.

This is the first time the merge request is approved. To ensure full test coverage, please start a new pipeline before merging.

For more info, please refer to the following links:

added pipeline:mr-approved label

@peterhegman, thanks for approving this merge request.

This is the first time the merge request has been approved. Please wait for AppSec approval before merging.

cc @gitlab-com/gl-security/appsec this is a JiHu contribution, please follow the JiHu contribution review process.

Refactor: user profile page to Vue

What does this MR do and why?

Screenshots or screen recordings

How to set up and validate locally

MR acceptance checklist

Activity

Reviewer roulette

Reviewer roulette

Allure report

Refactor: user profile page to Vue

What does this MR do and why?

Screenshots or screen recordings

How to set up and validate locally

MR acceptance checklist

Merge request reports

Activity

Reviewer roulette

Reviewer roulette

Allure report