You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently have the api/reviews/all API endpoint that lets us fetch reviews based on their status: expired, pending, active, or merged. However, we are missing one important status: rejected reviews. These are reviews where the pull request (PR) was closed without merging.
Identifying Rejected Reviews
A review can be classified as 'rejected' if it meets all of the following criteria (to be confirmed by @Extheoisah):
The review has been submitted.
It has not been merged.
It has been archived.
Proposed Change
We need to update the api/reviews/all endpoint to include 'rejected' as a status option. This will allow us to track and manage these reviews more effectively, ensuring that all types of review outcomes are visible and accounted for in our system.
The text was updated successfully, but these errors were encountered:
This commit adds
1. the functionality to compute the review status for all reviews when queried from the database. This computation is done on the API level and is not stored in the db.
2. a new "rejected" review status based on the criteria outlined [here](#294)
We currently have the
api/reviews/all
API endpoint that lets us fetch reviews based on their status: expired, pending, active, or merged. However, we are missing one important status: rejected reviews. These are reviews where the pull request (PR) was closed without merging.Identifying Rejected Reviews
A review can be classified as 'rejected' if it meets all of the following criteria (to be confirmed by @Extheoisah):
Proposed Change
We need to update the
api/reviews/all
endpoint to include 'rejected' as a status option. This will allow us to track and manage these reviews more effectively, ensuring that all types of review outcomes are visible and accounted for in our system.The text was updated successfully, but these errors were encountered: