admin-requests
admin-requests copied to clipboard
conda-forge
Some issues cropped up recently with `conda-build` version `24.5.0` and our package validation tooling ( https://github.com/conda-forge/conda-forge-ci-setup-feedstock/issues/317 ) This marks `conda` & `conda-build` version `24.5.0` broken while we work out those...
### Comment: ## elevator pitch Provide a low-barrier way to make precise, pre-validated admin requests. ## motivation After looking at the GH PR templates feature (suggested in #535), I was...
## Guidelines for marking packages as broken: * We prefer to patch the repo data (see [here](https://github.com/conda-forge/conda-forge-repodata-patches-feedstock)) instead of marking packages as broken. This alternative workflow makes environments more reproducible....
## Guidelines for marking packages as broken: * We prefer to patch the repo data (see [here](https://github.com/conda-forge/conda-forge-repodata-patches-feedstock)) instead of marking packages as broken. This alternative workflow makes environments more reproducible....
Both of these packages have a checksum mistmach and do not download and install. ## Guidelines for marking packages as broken: * We prefer to patch the repo data (see...
## Guidelines for marking packages as broken: * We prefer to patch the repo data (see [here](https://github.com/conda-forge/conda-forge-repodata-patches-feedstock)) instead of marking packages as broken. This alternative workflow makes environments more reproducible....
I brought up https://github.com/conda-forge/conda-forge.github.io/issues/1972 in a core call recently, and @jaimergp mentioned that this should be done through admin-requests for traceability reasons. I'm game to give this a shot at...
### Comment: I'm a maintainer of the package **pyam** (https://github.com/conda-forge/pyam-feedstock), but for some reasons in its early days, this package was published as **pyam-iamc** on Pypi. I recently played around...
The previous build was triggered from a push directly into the feedstock. The new build (1) is there, just need to mark the previous as broken. ## Guidelines for marking...
Currently we have this logic to prevent multiple runs on `main` for different commits: https://github.com/conda-forge/admin-requests/blob/cd3686599e10a654b7f4ec2a2cce46ab78db074b/.github/workflows/main.yml#L14-L20 Another option would be to use [GHA's `concurrency` syntax]( https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#concurrency ). Here's [an example]( https://github.com/dask/dask/blob/23a75632b7644f1289a760031d9ba85a35cbfd20/.github/workflows/conda.yml#L12-L16...