Mark the changes that are required to pass the review #120842
Unanswered
quilicicf
asked this question in
Pull Requests
Replies: 1 comment 1 reply
-
It sounds like you need a more integrated solution for managing comment severity and PR status. One approach could be to use a code review tool or platform that supports custom tagging or labeling of comments, along with automated status updates based on those tags. Have you considered using tools like GitHub with custom labels or integrating with third-party code review tools that offer more flexibility in managing comment severity? This could streamline the process and make it easier for both reviewers and authors to track and address comments effectively. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Select Topic Area
Product Feedback
Body
One thing I struggle with in a PR is marking the severity of the comments.
Basically, I like to annotate my comments with severity (not unlike what the folks at Netlify do).
The problem I have is that I need to have the pull request status reflect the comments:
And I need to have the author recognize what comment is at what level, potentially allowing them to sort by severity to address in descending order (and sometimes, minor issues asynchronously in another PR).
I currently do this with labels starting my review messages and leveraging the search feature of the web browser but that's not very integrated and the link between comment severity and PR status is manual.
I'd really like as a reviewer to have the capability of marking the comments' levels and have the right PR status pre-selected when I submit my review.
I'd really like as an author to have the ability to get the list of comments by severity to address them in descending order (and understand at a glance why the PR status is what it is).
Beta Was this translation helpful? Give feedback.
All reactions