Hello,
we recently setup a Gitea instance in our company which introduced quite a lot of new workflows for some developers. Now the problem is that even if we told all developers they should create API tokens for all the different workflows (e.g. repository access, reading packages etc.), they tend to just enter their regular password and it simply works. Is there a configuration for the whole Gitea instance to limit the user password to just the login of the Gitea UI and require every user to create API tokens for registering with the API for accessing repositories and packages and so on?
It’s a good proposal that we could have an option to disable password in API even with git clone.