Revise explanation of --project option

I need to introduce the idea that "projects" are actually file paths,
and that these paths are the keys for the key-value stores that are the
config files.

...but without saying "HashMap" because that's really an implementation
detail.
This commit is contained in:
2025-07-21 16:14:47 -05:00
parent 4b9257a9a7
commit b952e40060

View File

@@ -55,7 +55,7 @@ For details, see Gitea's documentation on [token scopes](https://docs.gitea.com/
### The `--project` option ### The `--project` option
Override the default (current-directory) project name when searching through the config files for this project's settings. Settings retrieved from config files are selected based on the project's path. By default, the current directory will be used. In case that guess is incorrect, this option can be specified with another path.
See [configuration](#configuration) for details on format and file locations. See [configuration](#configuration) for details on format and file locations.