@@ -130,7 +130,7 @@ Install the necessary dependency packages from conda-forge.
130130Remember that these must be executed within the `` metpy `` directory.
131131
132132``` sh
133- conda install --file ci/requirements.txt --file ci/extra_requirements.txt --file ci/ dev/test_requirements.txt
133+ conda install --file ci/requirements.txt --file ci/extra_requirements.txt --file ci- dev/test_requirements.txt
134134```
135135
136136Finally, create an editable install of MetPy that will update with your development!
@@ -204,7 +204,7 @@ your feature is more complex, consider adding to the examples or tutorials for M
204204You can build the documentation locally to see how your changes will look.
205205After setting up your [ development environment] ( #setting-up-your-development-environment ) above,
206206from within the `` metpy `` directory with your `` devel `` environment active,
207- use `` conda install --file ci/ dev/doc_requirements.txt ``
207+ use `` conda install --file ci- dev/doc_requirements.txt ``
208208to install required packages to build our documentation.
209209Then, still from within your `` devel `` environment,
210210
@@ -343,7 +343,7 @@ locally within the source directory you can use the [ruff](https://docs.astral.s
343343After setting up your [development environment](# setting-up-your-development-environment) above,
344344from within the ` ` metpy` ` directory with your ` ` devel` ` environment active,
345345install the code style tools we use with
346- ` ` conda install --file ci/ dev/linting_requirements.txt` ` . Checking your code style is then as
346+ ` ` conda install --file ci- dev/linting_requirements.txt` ` . Checking your code style is then as
347347easy as running ` ` ruff check . ; flake8 .` ` in the base of the repository.
348348
349349You can also just submit your PR and the kind robots will comment on all style violations as
0 commit comments