Skip to content

Don't train users to by-pass deletion confirmation #31309

Open
@jtran

Description

@jtran

Feature Description

The blog post How we lost 54k GitHub stars from HTTPie explains everything that I'm asking for. But the summary is that by having a confirmation to delete repositories that requires people to type something, even when the repository is empty, has no issues, no PRs, no stars, etc., it teaches and trains people to mindlessly by-pass the confirmation, which defeats the purpose of the confirmation, leading to permanent data loss.

I would like to see:

  1. When you delete a repository, display what else is going away with it in the confirmation dialog, such as how many issues, PRs, stars, releases, etc.
  2. If there's nothing else, don't require typing the repo name for extra confirmation in order to prevent training users to skip it without thinking on empty test repos, and save the tedious confirmation for when it really matters

Screenshots

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    proposal/acceptedWe have reviewed the proposal and agree that it should be implemented like that/at all.topic/ui-interactionChange the process how users use Gitea instead of the visual appearancetype/proposalThe new feature has not been accepted yet but needs to be discussed first.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions