feat(frontend): decide on a project in its review, and filter the queue - #258
Merged
Conversation
Approve and Reject now both live on the project's own page, under the description they judge. The queue gains Approved / Awaiting review / Rejected tabs and opens on Approved.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As an owner, I open a project, read it, and decide — Approve or Reject — right there. Before, I approved from a button on a list row without ever opening the project.
The queue now has three tabs, so I can look at just what's awaiting review, or just what I turned down, instead of scrolling one mixed list.
Left out: clearing a queue in one click each. That's the cost of deciding in a review, and it's the point. Participants are untouched — their list was already approved-only.