Select the types of activity you want to include in your feed.
@recaptime-dev's working patches + fork for Phorge, a community fork of Phabricator. (Upstream dev and stable branches are at upstream/main and upstream/stable respectively.)
hq.recaptime.dev/wiki/Phorge
···140140== Configuration ==
141141142142Some Arcanist commands can be configured. This configuration is read from
143143-several sources:
143143+three sources, in order:
144144145145- # A customization can force any setting with
146146- @{method@arcanist:ArcanistWorkingCopyIdentity::setRuntimeConfig}.
147147- # User can specify settings for working copy in `arc/config` file located in
148148- VCS directory (e.g. `.git/arc/config`) in JSON format. This file can also be
149149- modified by running `arc set-config --local`.
150150- # Repository can specify its config in `.arcconfig` in JSON format.
151151- # User can specify the settings in `~/.arcrc` (JSON) through the `config` key.
152152- This file can be modified also by `arc set-config --global`.
153153- # Machine can specify the settings with `/etc/arcconfig` (JSON). On Windows,
154154- the file path is `C:\ProgramData\Phabricator\Arcanist\config`.
145145+ # A project can specify configuration in an `.arcconfig` file. This file is
146146+ JSON, and can be updated using `arc set-config --local` or by editing
147147+ it manually.
148148+ # User configuration is read from `~/.arcconfig`. This file is JSON, and can
149149+ be updated using `arc set-config`.
150150+ # Host configuration is read from `/etc/arcconfig` (on Windows, the path
151151+ is `C:\ProgramData\Phabricator\Arcanist\config`).
155152156156-The first place where the setting is defined wins.
153153+Arcanist uses the first definition it encounters as the runtime setting.
157154158155Existing settings can be printed with `arc get-config`.
156156+157157+Use `arc help set-config` and `arc help get-config` for more information
158158+about reading and writing configuration.
159159160160== Next Steps ==
161161