-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a option "--user-type bot" to admin user create, improve role display #27885
Conversation
46b6867
to
44d63a7
Compare
ping? |
Partially solve go-gitea#13044
44d63a7
to
07e6c68
Compare
@typed-sigterm not sure what the ping was for, but in doubt, I rebased my PR. I still would like some feedback on the UI for the question of the subcommand |
Looks like https://github.com/go-gitea/gitea/pull/27885/files#r1380815227 is better to have. |
I will help to make some improvements, and fix more "bot" related logic |
Hmm, have a question here: should we allow bot users to login via password?
|
I don't think bot users should be allowed log in except access token cannot be generated at the moment. |
@mscherer @typed-sigterm could you help to confirm: whether we should allow the bot user to sign-in via password? |
@mscherer I will vote my approval. If you have time please take a look at the new logic:
Since these changes are still in main branch, they are open to change if there are some requirements (and we can add more comments and tests) |
* giteaofficial/main: Feature: Support workflow event dispatch via API (go-gitea#32059) Remove "class-name" from svg icon (go-gitea#33540) Add "No data available" display when list is empty (go-gitea#33517) Add a option "--user-type bot" to admin user create, improve role display (go-gitea#27885)
Partially solve #13044
Fix #33295