This repo is for making requests to conda-forge/core
for various administrative
tasks.
If you want to mark a package as broken on conda-forge
, send a Pull Request
adding a new .yml
file in requests
folder with a list of the full names of the packages
for which the broken
label will be added. See examples/example-broken.yml
for an example.
Guidelines for marking packages as broken:
conda-forge/core
) try to make a decision on these requests within 24 hours.If you want to remove the broken label from packages on conda-forge
, send a Pull Request
adding a new .yml
file in requests
folder with a list of the full names of the packages
for which the label broken
will be removed. See examples/example-not-broken.yml
for an example.
If you want to reset your feedstock token to fix issues with uploads, send a Pull Request
adding a new .yml
file in requests
folder with a list of the feedstock names
without -feedstock
. See examples/example-token-reset.yml
for an example.
(e.g., for python-feedstock
, the feedstocks list must contain python
).
If you want to request a feedstock to be archived, send a Pull Request
adding a new .yml
file in requests
folder with a list of the feedstock names
without -feedstock
. See examples/example-archive.yml
for an example.
(e.g., for python-feedstock
, the feedstocks list must contain python
).
For unarchiving, see examples/example-unarchive.yml
for an example.
For feedstocks that need to be archived, please leave an open issue with some details about why that decision was taken (e.g. it has been deprecated by a new feedstock), and link it in your PR description.
Certain CI resources are opt-in only. If you want to request access to these resources, please
submit a PR adding your feedstock name to a new .yml
file in requests
folder.
Available opt-in resources:
examples/example-travis.yml
open-gpu-server
(includes GPU CI and long-running builds): See examples/example-open-gpu-server.yml
.