Improve the UX around Backgrounded Mirror Creation
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start by tracing the backgrounded mirror creation flow and the mirror list actions for an in-progress mirror. Check how the pending flash is shown and cleared, then verify that completion is announced, incomplete mirrors cannot be cloned, and rename/delete are unavailable with an explanation while creation is running.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem?
Currently the pending flash doesn't go away until the user dismisses it or refreshes and there is no notice provided when a backgrounded mirror creation completes. Due to the chunked pushes, the repo is populated from old to new and users could potentially clone down an incomplete mirror. The in-progress mirror also appears in the mirror list and has options to rename or delete it which could break things.
Describe the solution you'd like
The mirror creation UX should be enhanced to notify the user when a backgrounded mirror creation completes and a mirror that is still being created should not be able to be renamed or deleted with some indication to the user as to why.
Describe alternatives you've considered
No response
Additional context
Issues introduced and called out as part of https://github.com/github-community-projects/private-mirrors/pull/475
- Dominant language
- TypeScript
- Stars
- 203
- Forks
- 42
- Avg merge
- 1h 15m
- Merged PRs (30d)
- 8
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 github-community-projects/private-mirrors
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github-community-projects/private-mirrors#525 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
github-community-projects/private-mirrors#524 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-2 days Newbie friendliness 68/100
github-community-projects/private-mirrors#449 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
github-community-projects/private-mirrors#485 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
github-community-projects/private-mirrors#476 · 1 reaction ·
Maintainers usually reply within 1 day
All issues in github-community-projects/private-mirrors
Similar issues
-
no-repo-link tool-submission
Difficulty 1/5 Under an hour Newbie friendliness 66/100
BraveOPotato/NoSignups#2458 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
drmrd/vernacular#1061 ·
Maintainers usually reply within 1 day
-
[Bug] PUT /profiles/{id} silently drops design_prompt — designed voice profiles cannot be editedOpen
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
automated issue report
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
eventua11y/eventua11y.com#982 ·
Maintainers usually reply within 1 day