add subcomand admin #161
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/tea#161
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?
add a subcomand named admin witch with features like:
important use case: add users to org teams
I just want to know if the following would go into the right direction how the commands / sub commands should be structured: (based on the README I use the plural form whereas the singular should be handled via aliases):
tea admin users ...
tea admin organizations ...
tea admin teams ...
The relationship to the appropriate organizations can be done via an option like
--owner <name>
:Now the question how to handle add/remove of users to appropriate
orga
?Alternative via positional arguments? like:
(The existing command seemed to be going via
--owner ..
way)...tea admin repos ...
The relationship to the appropriate organizations can be done via an option like
--owner <name>
:I have started to create a basic foundation for the `admin´ commands https://gitea.com/khmarbaise/tea/src/branch/issue-161-admin-command (I don't want to make a PR of it yet because I'm not sure if the approache is the right way)...
I just want to know if this is the direction we could go?
Further acting would be to start with a pr for the foundation admin commands
and add several separate PR's for the implementation of each sub command...
admin subcomand is in one way special: we have to make sure the current user is an admin befor we do anthing more
moved new subcomand into new milestone, like to release v0.6.0 within december
so we should finish the "big refactor" & polish added feature + bugfixing ;)
@khmarbaise @noerw
I've started some automation via the
/teams
API endpoint to automatically add new users to certain orgs.Would be awesome if this could be supported via
tea
?@pat-s
nice idear, i wont have time to add it, but I'm happy to test and review pulls ;)