Introduce tea organizations area command #263
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#263
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?
I'm suggesting this cause I realized that the command
does not (yet) exist as well commands accordingly for the creation of organizations etc.
The question is: Is
tea
intended to make full administation/setup of Gitea possible in the future?I've started to play around a little bit for that:
a984d0e515
Yup, there should be another issue for admin commands even, to at least
ls
users on site, and create/update them w/ admin permissions.@techknowlogick Great to hear that. Related to #161
Second: Is the direction to create a set of sub commands to
organizations
like I suggested the right direction:Or should that being done different? Meaning only via
admin
instead? But If I correctly understood the permission concept a user can also generate an organization?So based on my experiments the output of
tea orgs ls
could like this: (Yes much debugging output in there):khmarbaise referenced this issue2020-12-05 21:49:08 +00:00
In theory both
tea admin orgs...
andtea orgs...
should work, but just like how we have the api split up they would serve different situations, even though they may be largely similar.So
admin orgs ..
as I described in #161 and separatetea orgs ..
ok..I thought so ..but wanted to be sure...admin orgs is only if you have admin access ...