new structure #184
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#184
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?
internal structure
(e.g. create token by user/passwd)
generell concepts
subcomands without args list objects (list issues/pulls/releases)
subsubcomand
ls
list obects with lots of filter optionssubsubcomand
create/edit
without arguments ask user interactivelysubsubcomand
create/edit
with arguments is controled fully by flagssubsubcomand
delete
show info what is deleted and ask user again, if force flag-y
is not setif subsubcomand refer to objects again, just follow subsubsub comand style as abouve ...
I agree with the general concepts.
I don't have an opinion on package structure, but agree that we need more separation of concerns
See also #37
good point, we have some work to do to get tea compliant to thos proposals :D
-> we should unify and write them into CONTRIBUTING.md, after work is done
Remaining things to refactor:
...?
created issues: #226 to #246
so we can close this for now :)