conda-forge is a community led collection of recipes, build infrastructure and distributions for the conda package manager.
Important git repositories for conda-forge documentation, status, and governance
- conda-forge.github.io - website, documentation, and tracker for general conda-forge problems and enhancements
- status - Repo for status page and to track service outages
- CFEP - Conda-forge Enhancement Proposals for defining community-wide policies
- marketing - Logos and other materials for conda-forge
- by-the-numbers - Notebooks and scripts to compute statistics about conda-forge
- conda-forge-metadata - API access to conda-forge's metadata
Important git repositories for users/maintainers
- staged-recipes - The place to submit new recipes
- admin-requests - GitHub repo to ask conda-forge/core for admin tasks like marking packages broken or archiving feedstocks
- conda-forge-repodata-patches-feedstock - Git repo that tracks hotfixing of package metadata
- conda-forge-pinning-feedstock - Global pinnings in conda-forge and migration information
- miniforge - An installer with conda-forge as the default channel
- conda-smithy - The tool for managing conda-forge feedstocks.
Other Infrastructure-related git repositories
- feedstocks - A monorepo containing all feedstocks as submodules
- feedstock-outputs - Repo holding the authoritative mapping between feedstocks and conda packages
- cdt-builds - All build recipes for the core dependency tree
- conda-forge-webservices - The source code to run conda-forge admin commands and linting
- docker-images - Docker images used to build conda-forge packages (
linux-*andnoarchonly) - conda-forge-ci-setup-feedstock - Build-time settings for each CI run
- admin-migrations - Admin related jobs for managing conda-forge
- webservices-dispatch-action - GitHub action for webservices jobs
- automerge-action - GitHub action for automerge service
- conda-forge-feedstock-ops - Containerized maintenance operations for feedstocks
