Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added precedence and conflict info #9565

Merged
merged 2 commits into from Jan 7, 2020
Merged

Conversation

rrigdon
Copy link
Contributor

@rrigdon rrigdon commented Jan 7, 2020

No description provided.

@rrigdon rrigdon requested a review from a team as a code owner January 7, 2020 21:13
@cla-bot cla-bot bot added the cla-signed [bot] added once the contributor has signed the CLA label Jan 7, 2020
The precedence by which the conda configuration is built out is shown below.
Each new arrow takes precedence over the ones before it. For example, config
files (by parse order) will be superceded by any of the other configuration
options and environment variables will always take precedence over the other 3.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be nice to mention how conda recognizes the config environment variables. They are of the form CONDA_<name of config parameter>

@github-actions
Copy link

Hi there, thank you for your contribution to Conda!

This pull request has been automatically locked since it has not had recent activity after it was closed.

Please open a new issue or pull request if needed.

@github-actions github-actions bot added the locked [bot] locked due to inactivity label Aug 22, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla-signed [bot] added once the contributor has signed the CLA locked [bot] locked due to inactivity
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants