Bugfixes for initCommand #156
No reviewers
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/tea#156
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "6543/tea:bugfix_loadConfig"
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?
Bugfix Loadconfigto Bugfixes for initCommandI guess this solves the bug for the present but this is all a bit convoluted
and quite difficult to understand - e.g. there's initCommandLoginOnly()
just below this that appears to use a different way of determining the login.
I think we need to explain these techniques for finding the login - make it
clear where ActiveLogin gets it's login from etc.