### Create and Activate Conda Environment Source: https://github.com/conda/conda-docs/blob/main/README.md Creates a new conda environment named 'conda-docs', installs pip, activates the environment, and installs dependencies from requirements.txt. This is the initial setup step for building the documentation locally. ```bash conda create -n conda-docs pip -y conda activate conda-docs pip install -r requirements.txt ``` -------------------------------- ### Install Miniconda with Homebrew Source: https://github.com/conda/conda-docs/blob/main/docs/source/index.md Use this command to install Miniconda if you have Homebrew package manager installed on your system. ```bash brew install miniconda ``` -------------------------------- ### Install Miniforge with Homebrew Source: https://github.com/conda/conda-docs/blob/main/docs/source/index.md Use this command to install Miniforge on macOS using the Homebrew package manager. Ensure Homebrew is installed and up to date before running this command. ```bash brew install miniforge ``` -------------------------------- ### Start Conda Development Environment (Bash) Source: https://github.com/conda/conda-docs/blob/main/docs/source/contributing.md Activate the local development environment for Conda. This command creates or activates the './devenv' environment. ```bash . dev/start ``` -------------------------------- ### Start Conda Development Environment (Windows CMD) Source: https://github.com/conda/conda-docs/blob/main/docs/source/contributing.md Activate the local development environment for Conda in Windows Command Prompt. This command creates or activates the './devenv' environment. ```cmd .\dev\start ``` -------------------------------- ### Run Conda Unit Tests with Pytest (Bash) Source: https://github.com/conda/conda-docs/blob/main/docs/source/contributing.md Execute Conda's unit tests using pytest. This command runs tests that are not marked as 'integration' or 'installed'. ```bash py.test -m "not integration and not installed" conda tests ``` -------------------------------- ### Build HTML Documentation Source: https://github.com/conda/conda-docs/blob/main/README.md Builds the HTML version of the documentation using the make command. The specific build commands are defined in the docs/Makefile. This command generates the output in the _build/html directory. ```bash make html ``` -------------------------------- ### Navigate to Docs Directory Source: https://github.com/conda/conda-docs/blob/main/README.md Changes the current directory to the 'docs' folder. This is a prerequisite for running the build commands. ```bash cd docs ``` -------------------------------- ### Run Conda Unit Tests with Make (Bash) Source: https://github.com/conda/conda-docs/blob/main/docs/source/contributing.md Execute the project's unit tests using the GNU make utility. This is a standard way to run tests in many development environments. ```bash make unit ``` -------------------------------- ### Set Conda Project Root Directory (Windows CMD) Source: https://github.com/conda/conda-docs/blob/main/docs/source/contributing.md Define the environment variable for the project's root directory in Windows Command Prompt. This is used for cloning the repository. ```cmd set "CONDA_PROJECT_ROOT=%HOMEPATH%\conda" ``` -------------------------------- ### Set Conda Project Root Directory (Bash) Source: https://github.com/conda/conda-docs/blob/main/docs/source/contributing.md Define the environment variable for the project's root directory. This is used for cloning the repository. ```bash CONDA_PROJECT_ROOT="$HOME/conda" ``` -------------------------------- ### Clone Conda Repository and Set Remote (Windows CMD) Source: https://github.com/conda/conda-docs/blob/main/docs/source/contributing.md Clone the conda repository and configure git remotes for your fork and the upstream repository in Windows Command Prompt. Ensure you have forked the repository first. ```cmd set GITHUB_USERNAME=kalefranz git clone git@github.com:conda/conda "%CONDA_PROJECT_ROOT%" cd "%CONDA_PROJECT_ROOT%" git remote add %GITHUB_USERNAME% git@github.com:%GITHUB_USERNAME%/conda ``` -------------------------------- ### Clone Conda Repository and Set Upstream (Bash) Source: https://github.com/conda/conda-docs/blob/main/docs/source/contributing.md Clone the conda repository and configure git remotes for your fork and the upstream repository. Ensure you have forked the repository first. ```bash GITHUB_USERNAME=kalefranz git clone git@github.com:$GITHUB_USERNAME/conda "$CONDA_PROJECT_ROOT" cd "$CONDA_PROJECT_ROOT" git remote add upstream git@github.com:conda/conda ``` -------------------------------- ### Mermaid Diagram for Issue Sorting Flow Source: https://github.com/conda/conda-docs/blob/main/HOW_WE_USE_GITHUB.md This Mermaid diagram illustrates the workflow of issue sorting within the GitHub issue tracker and its connection to the roadmap board. It visualizes the states from new issues to closed issues, including maintainer sorting and progression through different project boards. ```mermaid flowchart LR subgraph flow_sorting [Issue Sorting in Issue Tracker] state_sorting{{Maintainer sorting}} end subgraph flow_roadmap [Roadmap Board] board_refinement{{Refinement}} board_backlog{{Backlog}} board_refinement-->board_backlog board_backlog-- reprioritize -->board_backlog board_progress{{Current Sprint - In Progress}} end state_new(New Issues) state_closed(Closed) state_new-->state_sorting state_sorting-- accepted for work -->board_refinement state_sorting-- duplicate, off-topic, support resolved -->state_closed board_backlog-- pending work -->board_progress board_refinement-- not actionable -->state_closed board_backlog-- resolved, irrelevant -->state_closed board_progress-- resolved -->state_closed ``` -------------------------------- ### Run Specific Conda Test with Pytest (Bash) Source: https://github.com/conda/conda-docs/blob/main/docs/source/contributing.md Focus on running a specific test file and a particular test case using pytest. This is useful for debugging individual tests. ```bash py.test tests/test_create.py -k create_install_update_remove_smoketest ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.