Skip to content

feat(frontend): decide on a project in its review, and filter the queue - #258

Merged
sabinem merged 1 commit into
mainfrom
fix/projects
Aug 27, 2026
Merged

feat(frontend): decide on a project in its review, and filter the queue#258
sabinem merged 1 commit into
mainfrom
fix/projects

Conversation

@sabinem

@sabinem sabinem commented Aug 27, 2026

Copy link
Copy Markdown
Collaborator

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.

  • Two buttons per project, always: the two states it isn't in. Awaiting review → Approve · Reject. Approved → Revoke approval · Reject. Rejected → Approve · Reconsider.
  • Tabs are real addresses, so a filtered view can be bookmarked and the back button works.
  • Opens on Approved. The Awaiting review count shows as an amber badge — it asks for attention without moving where you land.
  • Deciding returns you to the tab you came from, so approving the last proposal lands on "Nothing is awaiting review" rather than quietly moving you.

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.

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.
@sabinem
sabinem merged commit 5a8dd1d into main Aug 27, 2026
2 checks passed
@sabinem
sabinem deleted the fix/projects branch August 27, 2026 06:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant