loading up the forgejo repo on tangled to test page performance
Document creating an API key from the CLI (#25504) (#25510)
Frontport of #25504
Credit to @lonix1
Co-authored-by: lonix1 <40320097+lonix1@users.noreply.github.com>
Co-authored-by: delvh <dev.lh@web.de>
+8
+8
docs/content/doc/administration/command-line.en-us.md
+8
docs/content/doc/administration/command-line.en-us.md
···
108
108
- `--all`, `-A`: Force a password change for all users
109
109
- `--exclude username`, `-e username`: Exclude the given user. Can be set multiple times.
110
110
- `--unset`: Revoke forced password change for the given users
111
+
- `generate-access-token`:
112
+
- Options:
113
+
- `--username value`, `-u value`: Username. Required.
114
+
- `--token-name value`, `-t value`: Token name. Required.
115
+
- `--scopes value`: Comma-separated list of scopes. Scopes follow the format `[read|write]:<block>` or `all` where `<block>` is one of the available visual groups you can see when opening the API page showing the available routes (for example `repo`).
116
+
- Examples:
117
+
- `gitea admin user generate-access-token --username myname --token-name mytoken`
118
+
- `gitea admin user generate-access-token --help`
111
119
- `regenerate`
112
120
- Options:
113
121
- `hooks`: Regenerate Git Hooks for all repositories