Refactor flags.go and config.go #158
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#158
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?
-> make it "functional" again - at the moment it is not written as a normal functinal-lang-program intend to work
as mentioned by @zeripath in #156 too
unify initCommandLoginOnly() and initCommand()
@6543 I propose to change the call signature of InitCommand(), to return all context generated during initialization to any command:
Passing cli.Context in, we should be able to remove global flag variables, right?
@noerw not a bad idear, yes this should do it
Let me have a look at it once #285 got merged
befor introducing a TeaContext ... we should make sure Config is loeaded and not every module can acces the config var as it like to ...
-> #288