5 Commits (33850a83fe4ebd23a762a7aac81614c42e303bfa)

Author	SHA1	Message	Date
Cheng	9de443ced2	chore: use errors.New to replace fmt.Errorf with no parameters will much better (#30621) ... use errors.New to replace fmt.Errorf with no parameters will much better	7 months ago
JakobDev	c548dde205	More refactoring of `db.DefaultContext` (#27083) ... Next step of #27065	1 year ago
Yarden Shoham	d36ddfe26c	Fix CLI allowing creation of access tokens with existing name (#26071) ... We are now: - Making sure there is no existing access token with the same name - Making sure the given scopes are valid (we already did this before but now we have a message) The logic is mostly taken from a12a5f3652/routers/api/v1/user/app.go (L101-L123) Closes #26044 Signed-off-by: Yarden Shoham <git@yardenshoham.com>	1 year ago
wxiaoguang	d0dbe52e76	Refactor to use urfave/cli/v2 (#25959) ... Replace #10912 And there are many new tests to cover the CLI behavior There were some concerns about the "option order in hook scripts" (https://github.com/go-gitea/gitea/pull/10912#issuecomment-1137543314), it's not a problem now. Because the hook script uses `/gitea hook --config=/app.ini pre-receive` format. The "config" is a global option, it can appear anywhere. ---- ## ⚠️ BREAKING ⚠️ This PR does it best to avoid breaking anything. The major changes are: * `gitea` itself won't accept web's options: `--install-port` / `--pid` / `--port` / `--quiet` / `--verbose` .... They are `web` sub-command's options. * Use `./gitea web --pid ....` instead * `./gitea` can still run the `web` sub-command as shorthand, with default options * The sub-command's options must follow the sub-command * Before: `./gitea --sub-opt subcmd` might equal to `./gitea subcmd --sub-opt` (well, might not ...) * After: only `./gitea subcmd --sub-opt` could be used * The global options like `--config` are not affected	1 year ago
zeripath	aa1d95300a	Add command to bulk set must-change-password (#22823) ... As part of administration sometimes it is appropriate to forcibly tell users to update their passwords. This PR creates a new command `gitea admin user must-change-password` which will set the `MustChangePassword` flag on the provided users. Signed-off-by: Andrew Thornton <art27@cantab.net>	2 years ago