Git Product home page Git Product logo

actions's Introduction

Conda Logo

GitHub Scheduled Tests Codecov Status CodSpeed Performance Benchmarks
GitHub Release Anaconda Package conda-forge Package

Conda is a cross-platform, language-agnostic binary package manager. It is the package manager used by Anaconda installations, but it may be used for other systems as well. Conda makes environments first-class citizens, making it easy to create independent environments even for C libraries. Conda is written entirely in Python, and is BSD licensed open source.

Conda is enhanced by organizations, tools, and repositories created and managed by the amazing members of the conda community. Some of them can be found here.

Installation

To bootstrap a minimal distribution, use a minimal installer such as Miniconda or Miniforge.

Conda is also included in the Anaconda Distribution.

Updating conda

To update conda to the newest version, use the following command:

$ conda update -n base conda

Tip

It is possible that conda update does not install the newest version if the existing conda version is far behind the current release. In this case, updating needs to be done in stages.

For example, to update from conda 4.12 to conda 23.10.0, conda 22.11.1 needs to be installed first:

$ conda install -n base conda=22.11.1
$ conda update conda

Getting Started

If you install the Anaconda Distribution, you will already have hundreds of packages installed. You can see what packages are installed by running:

$ conda list

to see all the packages that are available, use:

$ conda search

and to install a package, use

$ conda install <package-name>

The real power of conda comes from its ability to manage environments. In conda, an environment can be thought of as a completely separate installation. Conda installs packages into environments efficiently using hard links by default when it is possible, so environments are space efficient, and take seconds to create.

The default environment, which conda itself is installed into, is called base. To create another environment, use the conda create command. For instance, to create an environment with PyTorch, you would run:

$ conda create --name ml-project pytorch

This creates an environment called ml-project with the latest version of PyTorch, and its dependencies.

We can now activate this environment:

$ conda activate ml-project

This puts the bin directory of the ml-project environment in the front of the PATH, and sets it as the default environment for all subsequent conda commands.

To go back to the base environment, use:

$ conda deactivate

Building Your Own Packages

You can easily build your own packages for conda, and upload them to anaconda.org, a free service for hosting packages for conda, as well as other package managers. To build a package, create a recipe. Package building documentation is available here. See AnacondaRecipes for the recipes that make up the Anaconda Distribution and defaults channel. Conda-forge and Bioconda are community-driven conda-based distributions.

To upload to anaconda.org, create an account. Then, install the anaconda-client and login:

$ conda install anaconda-client
$ anaconda login

Then, after you build your recipe:

$ conda build <recipe-dir>

you will be prompted to upload to anaconda.org.

To add your anaconda.org channel, or other's channels, to conda so that conda install will find and install their packages, run:

$ conda config --add channels https://conda.anaconda.org/username

(replacing username with the username of the person whose channel you want to add).

Getting Help

Contributing

open in gitpod for one-click development

Contributions to conda are welcome. See the contributing documentation for instructions on setting up a development environment.

actions's People

Contributors

beeankha avatar conda-bot avatar dbast avatar dependabot[bot] avatar dholth avatar jaimergp avatar jezdez avatar kenodegard avatar pre-commit-ci[bot] avatar

Stargazers

 avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

actions's Issues

Remove unused actions

Checklist

  • I added a descriptive title
  • I searched open requests and couldn't find a duplicate

What is the idea?

Both issue-in-project and user-in-team actions are unused. Given the relative complexity of these actions, they should be removed to discourage future use. A composite action will be a much better choice if the functionality is needed.

Why is this needed?

Unused actions only collect tech debt.

What should happen?

Remove issue-in-project and user-in-team actions.

Additional Context

No response

Create new release to be useable for osx-arm64 aka Apple Silicon Runners

Checklist

  • I added a descriptive title
  • I searched open requests and couldn't find a duplicate

What is the idea?

The canary release action was already updated to setup-miniconda@v3 (compatible with Apple Silicon Runners) via #141 but no release was done since then.

Why is this needed?

No response

What should happen?

A release to be tagged.

Additional Context

No response

Auto-create CLA signee PR for new contibutors

What is the idea?

Whenever a contributor opens a PR and their username is NOT found in the .clabot file, open a PR against the .clabot file adding the contributor to the file.

Why is this needed?

Reduce CLA signature verification effort.

What should happen?

Update CLA action to automatically create a new PR here with the new contributor.

Who owns this repo?

What is the idea?

Who owns this repo and is responsible for code reviews & releases?

@conda/infrastructure or some other team? A new team?

Why is this needed?

So we can add a CODEOWNERS file.

Add cleanup functionality for the canary-release workflow

We should add an option cleanup feature to the canary-release workflow that allows deleting the channel's N packages (or by time) automatically when running the workflow. That way we reduce the risk of overflowing the hard disk limits of anaconda.org account (10G).

Improved reporting on the `template-files` action

Checklist

  • I added a descriptive title
  • I searched open requests and couldn't find a duplicate

What is the idea?

Implement a step summary (and include the same report in the PR) describing the files templated (the stubs they requested/used) and any unused stubs.

Why is this needed?

Improved transparency on where files come from and how they get rendered.

What should happen?

Update template-files to produce a GITHUB_STEP_SUMMARY at the end of the job. This summary will then be accessible at the completion of the workflow in the GH Action summary page. We'd also like to include this info in the PR that gets created for easier audits.

Additional Context

No response

Release 24.4.0

Checklist

  • I added a descriptive title
  • I searched open requests and couldn't find a duplicate

What is the idea?

Cut a new release with the recent conda-incubator/setup-miniconda version bump.

Why is this needed?

Resolve downstream issues with canary builds for osx-64 versus osx-arm64.

What should happen?

No response

Additional Context

No response

`combine-durations` detects repo from cloned repo, not based on the repo the workflow lives in

Checklist

  • I added a descriptive title
  • I searched open reports and couldn't find a duplicate

What happened?

There are two conditions in which combine-durations may be triggered. The most common situation is via a scheduled run (see https://github.com/conda/conda/actions/runs/10232908263/job/28310609789) but with the new update.yml workflow the action may also be triggered manually (see https://github.com/conda/conda/actions/runs/10255189131/job/28371616702).

In either case if no PR exists then we end up cloning the upstream repo allowing combine-durations to correctly detect the repository to download artifacts from. However, if a PR already exists (which typically means the PR is made via a fork) then combine-durations will incorrectly detect the fork repo as the upstream and will attempt to download test artifacts from the fork (of which there will be none).

Conda Info

No response

Conda Config

No response

Conda list

No response

Additional Context

No response

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.