Skip to content
Snippets Groups Projects

Added finish review dropdown

Merged Phil Hughes requested to merge ph/244044/submitReviewWithComment into master
1 unresolved thread

What does this MR do and why?

Adds a finish review dropdown to the merge request reviews bar that allows users to add a comment when submitting a review.

Screenshots or screen recordings

Screenshot_2022-06-08_at_11.08.25

How to set up and validate locally

Enable mr_review_submit_comment

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Closes #244044 (closed)

Edited by Phil Hughes

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • 2 Warnings
    :warning: This merge request is quite big (607 lines changed), please consider splitting it into multiple merge requests.
    :warning:

    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:

    1 Message
    :book: CHANGELOG missing:

    If you want to create a changelog entry for GitLab FOSS, add the Changelog trailer to the commit message you want to add to the changelog.

    If you want to create a changelog entry for GitLab EE, also add the EE: true trailer to your commit message.

    If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.

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

    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 George Koltsov (@georgekoltsov) (UTC+1, same timezone as @iamphill) Sean Arnold (@seanarnold) (UTC+12, 11 hours ahead of @iamphill)
    frontend Mireya Andres (@mgandres) (UTC+8, 7 hours ahead of @iamphill) Michael Lunøe (@mlunoe) (UTC+2, 1 hour ahead of @iamphill)
    test Quality for spec/features/* John McDonnell (@john.mcdonnell) (UTC+12, 11 hours ahead of @iamphill) Maintainer review is optional for test Quality 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.

    Generated by :no_entry_sign: Danger

  • Bundle size analysis [beta]

    This compares changes in bundle size for entry points between the commits daa997b4 and ddf3a6b8

    :sparkles: Special assets

    Entrypoint / Name Size before Size after Diff Diff in percent
    mainChunk 1.93 MB 1.93 MB +6.22 KB 0.3 %
    average 3.46 MB 3.46 MB +4.48 KB 0.1 %

    :tada: Significant Reduction: 5

    Expand
    Entrypoint / Name Size before Size after Diff Diff in percent
    pages.admin.groups.new 161.66 KB 24.17 KB -137.5 KB -85.1 %
    pages.admin.groups.edit 210.29 KB 73.19 KB -137.1 KB -65.2 %
    pages.groups.new 216.9 KB 140.5 KB -76.39 KB -35.2 %
    pages.dashboard.groups.index 271.79 KB 261.73 KB -10.06 KB -3.7 %
    pages.explore.groups 273.63 KB 263.56 KB -10.06 KB -3.7 %

    Note: We do not have exact data for daa997b4. So we have used data from: db83a152.
    The target commit was too new, so we used the latest commit from master we have info on.
    It might help to rerun the bundle-size-review job
    This might mean that you have a few false positives in this report. If something unrelated to your code changes is reported, you can check this comparison in order to see if they caused this change.

    Please look at the full report for more details


    Read more about how this report works.

    Generated by :no_entry_sign: Danger

  • Allure report

    allure-report-publisher generated test report!

    review-qa-blocking: :exclamation: test report for ddf3a6b8

    expand test summary
    +---------------------------------------------------------------------------+
    |                              suites summary                               |
    +----------------------+--------+--------+---------+-------+-------+--------+
    |                      | passed | failed | skipped | flaky | total | result |
    +----------------------+--------+--------+---------+-------+-------+--------+
    | Package              | 0      | 0      | 1       | 0     | 1     | ➖     |
    | Plan                 | 48     | 0      | 1       | 48    | 49    | ❗     |
    | Verify               | 12     | 0      | 1       | 12    | 13    | ❗     |
    | Protect              | 2      | 0      | 0       | 2     | 2     | ❗     |
    | Manage               | 36     | 0      | 2       | 37    | 38    | ❗     |
    | Create               | 23     | 0      | 2       | 22    | 25    | ❗     |
    | Secure               | 6      | 0      | 0       | 6     | 6     | ❗     |
    | Configure            | 0      | 0      | 1       | 0     | 1     | ➖     |
    | Version sanity check | 0      | 0      | 1       | 0     | 1     | ➖     |
    +----------------------+--------+--------+---------+-------+-------+--------+
    | Total                | 127    | 0      | 9       | 127   | 136   | ❗     |
    +----------------------+--------+--------+---------+-------+-------+--------+

    package-and-qa-ff-disabled: :exclamation: test report for ddf3a6b8

    expand test summary
    +---------------------------------------------------------------------------+
    |                              suites summary                               |
    +----------------------+--------+--------+---------+-------+-------+--------+
    |                      | passed | failed | skipped | flaky | total | result |
    +----------------------+--------+--------+---------+-------+-------+--------+
    | Verify               | 120    | 0      | 9       | 0     | 129   | ✅     |
    | Create               | 441    | 0      | 24      | 8     | 465   | ❗     |
    | Fulfillment          | 6      | 0      | 33      | 0     | 39    | ✅     |
    | Manage               | 303    | 0      | 12      | 1     | 315   | ❗     |
    | Plan                 | 159    | 0      | 0       | 0     | 159   | ✅     |
    | Secure               | 60     | 0      | 6       | 3     | 66    | ❗     |
    | Configure            | 0      | 0      | 9       | 0     | 9     | ➖     |
    | Release              | 18     | 0      | 0       | 0     | 18    | ✅     |
    | Version sanity check | 0      | 0      | 3       | 1     | 3     | ➖     |
    | Package              | 0      | 0      | 9       | 0     | 9     | ➖     |
    | Product Intelligence | 6      | 0      | 0       | 0     | 6     | ✅     |
    | Protect              | 6      | 0      | 0       | 0     | 6     | ✅     |
    +----------------------+--------+--------+---------+-------+-------+--------+
    | Total                | 1119   | 0      | 105     | 13    | 1224  | ❗     |
    +----------------------+--------+--------+---------+-------+-------+--------+

    package-and-qa-ff-enabled: :exclamation: test report for ddf3a6b8

    expand test summary
    +---------------------------------------------------------------------------+
    |                              suites summary                               |
    +----------------------+--------+--------+---------+-------+-------+--------+
    |                      | passed | failed | skipped | flaky | total | result |
    +----------------------+--------+--------+---------+-------+-------+--------+
    | Plan                 | 159    | 0      | 0       | 0     | 159   | ✅     |
    | Secure               | 60     | 0      | 6       | 2     | 66    | ❗     |
    | Manage               | 303    | 0      | 12      | 1     | 315   | ❗     |
    | Create               | 441    | 0      | 24      | 8     | 465   | ❗     |
    | Verify               | 120    | 0      | 9       | 0     | 129   | ✅     |
    | Configure            | 0      | 0      | 9       | 0     | 9     | ➖     |
    | Fulfillment          | 6      | 0      | 33      | 0     | 39    | ✅     |
    | Package              | 0      | 0      | 9       | 0     | 9     | ➖     |
    | Version sanity check | 0      | 0      | 3       | 0     | 3     | ➖     |
    | Product Intelligence | 6      | 0      | 0       | 0     | 6     | ✅     |
    | Protect              | 6      | 0      | 0       | 0     | 6     | ✅     |
    | Release              | 18     | 0      | 0       | 0     | 18    | ✅     |
    +----------------------+--------+--------+---------+-------+-------+--------+
    | Total                | 1119   | 0      | 105     | 11    | 1224  | ❗     |
    +----------------------+--------+--------+---------+-------+-------+--------+
  • requested review from @annabeldunstone

  • Phil Hughes added 724 commits

    added 724 commits

    Compare with previous version

  • Annabel Dunstone Gray changed the description

    changed the description

    • Resolved by Phil Hughes

      @iamphill This is looking great!!! :star: I have a few questions/comments:

      1. Will approvals be added in a separate MR?
      2. Slash commands/mentioning users doesn't autocomplete (it does work on submit though)
      3. On submit, user should be redirected to that comment on the Overview tab (I think we should do this in the first iteration, but I'm wondering if users would prefer to instead stay on the Changes tab and add a toast that says Review submitted :thinking: I'll look into this later)
      4. What are our options for making the Write/Preview buttons follow our tab design more closely? The main problem I see with the current implementation is that when you're on a tab, you don't actually have any visual indicator telling you which tab you're on
  • removed review request for @annabeldunstone

  • Phil Hughes changed the description

    changed the description

  • Phil Hughes added 1010 commits

    added 1010 commits

    Compare with previous version

  • Phil Hughes
  • requested review from @annabeldunstone

  • Phil Hughes added 160 commits

    added 160 commits

    Compare with previous version

  • Can we make the "Finish review" button secondary? I just realized we're probably not meant to have so many primary buttons next to each other

  • removed review request for @annabeldunstone

  • Phil Hughes marked this merge request as ready

    marked this merge request as ready

  • Phil Hughes added 1 commit

    added 1 commit

    • e1bb1cec - Scroll to note that was posted

    Compare with previous version

  • Phil Hughes added 1 commit

    added 1 commit

    • 211d9bf2 - Added spec for drafts controller

    Compare with previous version

  • requested review from @annabeldunstone

  • Phil Hughes requested review from @garyh

    requested review from @garyh

  • Annabel Dunstone Gray approved this merge request

    approved this merge request

  • removed review request for @annabeldunstone

  • :wave: @annabeldunstone, thanks for approving this merge request.

    This is the first time the merge request is approved. To ensure full test coverage, a new pipeline has been started.

    For more info, please refer to the following links:

  • Phil Hughes added 1 commit

    added 1 commit

    • ddf3a6b8 - Use GitLab UI components for form

    Compare with previous version

  • Gary Holtz approved this merge request

    approved this merge request

  • Phil Hughes requested review from @kushalpandya

    requested review from @kushalpandya

  • Gary Holtz removed review request for @garyh

    removed review request for @garyh

  • Kushal Pandya approved this merge request

    approved this merge request

  • Kushal Pandya unapproved this merge request

    unapproved this merge request

  • Kushal Pandya
  • Kushal Pandya approved this merge request

    approved this merge request

  • Thanks @iamphill, left a minor suggestion, looks good otherwise. :slight_smile:

  • Kushal Pandya removed review request for @kushalpandya

    removed review request for @kushalpandya

  • Phil Hughes requested review from @kushalpandya

    requested review from @kushalpandya

  • Kushal Pandya resolved all threads

    resolved all threads

  • Kushal Pandya enabled an automatic merge when the pipeline for 6aecd6d7 succeeds

    enabled an automatic merge when the pipeline for 6aecd6d7 succeeds

  • merged

  • Kushal Pandya mentioned in commit e5d1d562

    mentioned in commit e5d1d562

  • added workflowstaging label and removed workflowcanary label

  • 789 &:focus:active {
    790 box-shadow: inset 0 -#{$gl-border-size-2} 0 0 var(--gl-theme-accent, $theme-indigo-500),
    791 $focus-ring;
    792 @include gl-outline-none;
    793 }
    794 }
    795 }
    796 }
    797
    798 .gl-new-dropdown-contents {
    799 padding: $gl-spacing-scale-4 !important;
    800 }
    801
    802 .md-preview-holder {
    803 max-height: 180px;
    804 height: 180px;
  • mentioned in merge request !93124 (closed)

  • mentioned in issue #368916 (closed)

  • removed documentation label

  • mentioned in merge request !93725 (merged)

  • Please register or sign in to reply
    Loading