10 docs tagged with "how-to"

The following how-to guides are available in this category:

The following how-to guides are available in this category:

The following how-to guides are available in this category:

By default, feedstocks are created with support for the main platforms (e.g. linux-64, osx-64, win-64). Additional ones may be available in an opt-in fashion. The configuration can be changed manually in conda-forge.yml, or through automated migrations.

The conda-forge workflow assumes that contributors will always open their pull requests from their feedstock fork. Follow these best practices to make sure your branches are always up-to-date.

The conda-forge workflow assumes that a push to any branch in the feedstock repository will result in a build being uploaded to the conda-forge channel (and that's why PRs must always be opened from a fork!).

Perhaps one of the hardest tasks of package maintenance is ensuring that the recipe specifies

Rerendering is the process of regenerating the templated contents of your feedstock, according to the contents of conda-forge.yml and the recipe itself.

Some parts of the conda-forge automation are exposed as "bot commands" that can be invoked from issue titles and comments. You can check the full list in the admin-web-services documentation.

What to expect