Skip to content

Commit dcfe841

Browse files
zklausjaimergp
andcommitted
Change section title
Co-authored-by: jaimergp <[email protected]>
1 parent b867b4e commit dcfe841

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/maintainer/infrastructure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -468,7 +468,7 @@ uploaded from the new feedstock, by design.
468468
Once this is done correctly and the package is uploaded,
469469
you can then request the conda-forge core devs to archive the old feedstock.
470470

471-
## How package building interacts with infrastructure
471+
## Stages of package building and involved infrastructure
472472

473473
Packages in conda-forge are almost[^manual-builds] always built through CI.
474474
However, when a new package enters conda-forge for the first time, it does so via a pull request in the [`staged-recipes` repository](#staged-recipes), whereas every new build of the package after that is built in its repository, the so-called feedstock.

0 commit comments

Comments
 (0)