[UX] Manual import occupied-destination rejection does not say how to proceed
Maintainers usually reply within 7 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 63/100
Research direction
Start by reading issue #217 and trace the manual import rejection message for an occupied destination; the payload does not name a file or test. Add a short hint explaining the available next steps: remove or track the existing file, or choose replace. Done when the rejection tells users how to proceed.
Written by the indexing model from the issue text.
Description
Problem
The rejection shown for a manual import onto an occupied destination (#217) says what is in the way but not what to do (remove or track the existing file, or choose replace). A short hint would make it actionable. Found while reviewing #217.
- Dominant language
- C#
- Stars
- 664
- Forks
- 48
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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 Chaptarr/chaptarr
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 7 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Chaptarr/chaptarr#313 · 1 comment ·
Maintainers usually reply within 7 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 7 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 7 days
-
[BUG] CommandQueueManager.PushMany only dedupes against the queue snapshot, not within its own batchOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 7 days
All issues in Chaptarr/chaptarr
Similar issues
-
python triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
microsoft/semantic-kernel#14615 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
vzeol/DeployCraft#125 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
fboucher/2d6-dungeon-app#245 · 1 comment ·
Maintainers usually reply within 1 day
-
area: settings good first issue priority: p2 type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
AmineChr54/umbra#3 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day