Skip to content

feat: Revise peer review process

Edouard Legoupil requested to merge feature-peer-review-revamp into main_dev

Created by: Edouard-Legoupil

  • Adds thumbs-up and thumbs-down icons to each section

  • Conditionally renders a comment box on the right side of the section when a user clicks on the thumbs-down icon

  • Enables peer review finalization only when all sections have been reviewed

  • Adds a modal window to inform users about incomplete reviews

  • Removes duplicate action buttons from the header

  • Does my code meet the quality standards for releasing packages?

  • Does the reviewer have all the information to validate the features/issues without too much research?

  • Does the customer who will validate the associated tickets have the information to do so without wasting time?

Issues to validate to close :

  • issue #

Processed issues to keep open or in progress:

  • issue #

Checklist:

  • Does the package check go local?
  • Does the CI pass?
  • Are the added / fixed features documented, tested?
  • Are the added features / solved problems briefly presented in the PR message?
  • Are the changes related to tickets / issues that I have listed in the commits and in the PR itself?
  • Are the tickets in "review" mode in the Project Tracking Board?
  • Does each ticket, if it is to be closed after acceptance of the PR, contain a comment that tells how to validate it?

Merge request reports