Skip to content

Commit 1ae5f03

Browse files
committed
Fixing typos: conda-forge.yaml -> conda-forge.yml
1 parent c5abef4 commit 1ae5f03

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

scripts/regenerate_feedstock.py

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -207,7 +207,7 @@ def create_update_pr(clone, remote_head, fork_remote, upstream_remote):
207207
208208
I've re-rendered this feedstock with the latest version of conda-smithy ({}) and noticed some changes.
209209
If the changes look good, then please go ahead and merge this PR.
210-
If you have any questions about the changes though, please feel free to ping the 'conda-forge/core' team (using the @ notation in a comment).
210+
If you have any questions about the changes though, please feel free to ping the 'conda-forge/core' team (using the @ notation in a comment).
211211
212212
Remember, for any changes to the recipe you would normally need to increment the version or the build number of the package.
213213
Since this is an infrastructural change, we don't actually need/want a new version to be uploaded to anaconda.org/conda-forge, so the version and build/number are left unchanged and the CI has been skipped.
@@ -264,7 +264,7 @@ def create_update_pr(clone, remote_head, fork_remote, upstream_remote):
264264

265265
# Technically, we can do whatever we like to the feedstock now. Let's just
266266
# update the feedstock though. For examples of other things that *have* been
267-
# done here - once upon a time @pelson modified the conda-forge.yaml config
267+
# done here - once upon a time @pelson modified the conda-forge.yml config
268268
# item for every single feedstock, and submitted PRs for every project.
269269
conda_smithy.configure_feedstock.main(feedstock.directory)
270270
if pr:

src/maintainer/maintainer_faq.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -77,11 +77,11 @@ FAQ
7777

7878
You can configure the conda-forge CI to run a debug build using the mamba solver with the following changes:
7979

80-
- Set ``build_with_mambabuild: True`` in ``conda-forge.yaml`` file
80+
- Set ``build_with_mambabuild: True`` in ``conda-forge.yml`` file
8181
- Rerender with ``conda-smithy`` (to rerender manually use ``conda smithy rerender`` from the command line)
82-
82+
8383
.. note::
84-
84+
8585
Builds made with ``mambabuild`` won't be uploaded to ``conda-forge``. These builds are purely for debugging purposes.
8686

8787
You can also do this locally by using:

0 commit comments

Comments
 (0)