drop features to improve usability #379
I have the impression that usability of tea is rather low, as it tries to accomodate far too many different workflows for the same tasks (and lacks documentation for assumptions).
The flags needed for this create confusion as they target the same entities in different ways.
To simplify things, I propose to
It currently allows specifying remote repos via
owner/reposlugs, and local repos via a local directory path. #378 is a problem that results from this.
→ remove ability to specify local paths. If you need context of a local repo, just
cdto it first.
If dropping that usecase seems like a bad idea (please report!), an alternative would be to decouple both concepts and have a separate
--local-repoflag for this.
This flag can be used to specify a different remote in the local repo to detect a different remote repo than the default (which is derived from the local master branch).
I personally never used it, and talking to users (N=4) this seems to create quite some confusion.
If you need to specify a different remote repo, just use the
Simplify specifying remote repos for
tea pr create. Currently, overriding the base repo is done via the
--repoflag, but overriding the head repo is done by using an arcane head branch specifier
I don't know which syntax to settle on, but mixing these seems bad.
Document assumptions about workflows with tea. i.e. things like
- tea works best in a upstream/fork workflow, when the main branch tracks the upstream repo
drop SSH support entirely, we can authenticate everything with the access token we store already (only a user facing change with regard to login-setup).
If you have thoughts about further simplification of the CLI, write them up here! ;)
No due date set.
No dependencies set.
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?