Contributing to conda-forge

Report an issue with a package

• Search for the appropriate feedstock repository. The list of existing feedstocks is a good place to start.
• Take a look to see if the issue has already been raised on the feedstock's issue tracker. Otherwise, create a new issue, providing appropriate information, such as your operating system, package versions and an reproducible example of the problem. Even better, if you can automate the test in the conda recipe, it might be worth submitting a PR containing the test.
• Can't find the feedstock? No worries, just raise the issue at conda-forge/conda-forge.github.io and we will make sure the right people see it.

Update a package

• Search for the appropriate feedstock repository. The list of existing feedstocks is a good place to start.
• Fork the feedstock you wish to update
• Edit the recipe as desired. You may even consider adding yourself as a recipe maintainer.
• Propose the change as a pull request. Your recipe will automatically be built on Windows, Linux and OSX to test that it works, but the new distribution will not yet be available on the conda-forge channel.
• Once the recipe is ready it will be merged. The recipe will then automatically be built and uploaded to the conda-forge channel.

Add a recipe

• Fork conda-forge/staged-recipes
• Add a new conda recipe in the "recipes" directory. There is an example of a well written recipe there. Further guidance on writing good recipes.
• Propose the change as a pull request. Your recipe will automatically be built on Windows, Linux and OSX to test that it works, but the distribution will not yet be available on the conda-forge channel.
• Once the recipe is ready it will be merged and new "feedstock" repository will automatically be created for the recipe. The build and upload processes take place in the feedstock, and once complete the package will be available on the conda-forge channel