You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/maintainer/adding_pkgs.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -115,7 +115,7 @@ Post staging process
115
115
Feedstock repository structure
116
116
------------------------------
117
117
118
-
Once the PR having the recipe for a package is merged in the ``staged-recipes`` repository, a new repository is created automatically called ``<package-name> feedstock`` which lies in the `feestock<https://github.com/conda-forge/feedstocks/>`__ repository.
118
+
Once the PR having the recipe for a package is merged in the ``staged-recipes`` repository, a new repository is created automatically called ``<package-name> feedstock`` which lies in the `feedstock<https://github.com/conda-forge/feedstocks/>`__ repository.
119
119
A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configuration files for automatic building using freely available continuous integration services.
120
120
121
121
Each feedstock contains various files which are generated automatically using `conda-smithy <https://github.com/conda-forge/conda-smithy/>`__ which is a tool used for managing continuous integration and maintenance of the feedstocks. Broadly every feedstock has the following files :
0 commit comments