Make interactive issue/pull creation even if --repo flag is set #406
Labels
No Label
kind/breaking
kind/bug
kind/build
kind/dependency
kind/deployment
kind/docs
kind
enhancement
kind
feature
kind/proposal
kind
question
kind
refactor
kind/security
kind/testing
kind/translation
priority/critical
priority/high
priority/low
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
skip-changelog
status/blocked
status/has-backport
status/has-pull
status/needs-backport
status/needs-feedback
status/needs-reviews
status/wip
upstream/gitea
upstream/sdk
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/tea#406
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
for now you can not interactively create things if you have no local repo since you then have to specify the repo but you can not since if you do set it there is no interaction
to solfe it we could either allow --repo flag or ask on interaction mode for that info too
best case would be both
This highlights that flag parsing in urfave/cli is quite bad:
Not only is argument order rather inflexible, but also missing inheritance of flags:
In cobra, flags can be inherited from parent commands; with that we could put generic flags like
--repo
on the parent command, making the "no subcommand-specific flags passed" check that would be helpful for this usecase possible..