Supporting shortcuts like git branch -D some/branch to mean git branch --force --delete some/branch

[jabley]

As per the title. If I look at the help for git branch, I see:

        -d, --delete
           Delete a branch. The branch must be fully merged in its upstream branch, or in HEAD if no upstream was set with --track or --set-upstream-to.

       -D
           Shortcut for --delete --force.
        ...

        -f, --force
           Reset <branchname> to <start-point>, even if <branchname> exists already. Without -f, git branch refuses to change an existing branch. In combination with -d (or --delete),
           allow deleting the branch irrespective of its merged status, or whether it even points to a valid commit. In combination with -m (or --move), allow renaming the branch even
           if the new branch name already exists, the same applies for -c (or --copy).

           Note that git branch -f <branchname> [<start-point>], even with -f, refuses to change an existing branch <branchname> that is checked out in another worktree linked to the
           same repository.

I'm trying to do something similar with clap 4.5.4.

If I have

            .arg(
                clap::Arg::new("delete")
                    .required(false)
                    .short('d')
                    .long("delete")
                    .short_alias('D')
                    .action(clap::ArgAction::SetTrue),
            )
            .arg(
                clap::Arg::new("force")
                    .required(false)
                    .short('f')
                    .long("force")
                    .short_alias('D')
                    .action(clap::ArgAction::SetTrue),
            )

it fails with short option names must be unique, but '-D' is in use by both 'delete' and 'force'

What am I missing?

[epage]

We had #2836 which was trying to support this, both here and for subcommands but that ran into problems and we stopped that effort.

Allowing a short flag appear twice is an intriguing idea. My biggest concern is dealing with incompatible definitions of the two arguments and the help output (you wouldn't get that -D entry like git)

This can always be implemented manually with a helper unifying -D with -d and -f. You can also declare them as conflicting if need be. I believe this gets all of the user-visible effects you want with a little bit of user logic on your side.