Closed beckermr closed 2 years ago
Hi! This is the friendly automated conda-forge-linting service.
I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please try to merge or rebase with the base branch to resolve this conflict.
Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.
Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe
) and found it was in an excellent condition.
@conda-forge-admin rerender
@conda-forge-admin rerender
Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.
This message was generated by GitHub actions workflow run https://github.com/conda-forge/mpich-feedstock/actions/runs/2180991477.
added 3.x branch, if you want to retarget the PR. Probably want to add 3.x to bot.abi_migration_branches
in conda-forge.yml
@minrk @conda-forge/mpich this is ready for review and merge!
Checklist
0
(if the version changed)conda-smithy
(Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)This PR adds a build of 3x with run exports up to 5. The goal is to have a version that prevents excessive repodata patching in https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/issues/250.
We should merge this to a 3x branch in the upstream feedstock. I'm happy to maintain that.