Fix later-to-earlier reference (#3615)

## Summary

We generally consider things earlier in the array to be higher-priority,
and so that's where project-level settings go when merging.
This commit is contained in:
Charlie Marsh 2024-05-15 14:19:39 -04:00 committed by GitHub
parent a962a65302
commit 084529bad2
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions

View File

@ -230,7 +230,7 @@ If both project- and user-level configuration are found, the settings will be me
project-level configuration taking precedence. Specifically, if a string, number, or boolean is project-level configuration taking precedence. Specifically, if a string, number, or boolean is
present in both tables, the project-level value will be used, and the user-level value will be present in both tables, the project-level value will be used, and the user-level value will be
ignored. If an array is present in both tables, the arrays will be concatenated, with the ignored. If an array is present in both tables, the arrays will be concatenated, with the
project-level settings appearing later in the merged array. project-level settings appearing earlier in the merged array.
Settings provided via environment variables take precedence over persistent configuration, and Settings provided via environment variables take precedence over persistent configuration, and
settings provided via the command line take precedence over both. settings provided via the command line take precedence over both.