[Feature Request] Add a `Reason` when rejecting a puzzle
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
No file, test, or entry point is named. Start by locating the puzzle rejection flow and the place where puzzle status or review information is displayed; determine how a rejection reason would be stored, shown to other reviewers, and support returning a puzzle to pending. Done means reviewers can see the reason for a rejection.
Written by the indexing model from the issue text.
Description
Since we can have multiple people reviewing puzzles, it would be useful to know why a puzzle was rejected when that happens, so others can see the reason and maybe edit the puzzle and move it back to pending for example?
- Dominant language
- Ruby
- Stars
- 5
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fastruby/ruby_or_rails
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
fastruby/ruby_or_rails#129 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
fastruby/ruby_or_rails#75 · 1 comment · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
fastruby/ruby_or_rails#65 ·
All issues in fastruby/ruby_or_rails
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ai-generated
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
hanami/hanami-cli#449 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
hanami/hanami-router#310 ·