Conversation
|
@conda-forge-admin, please rerender |
|
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 ( I do have some suggestions for making it better though... For recipe/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/15570813092. Examine the logs at this URL for more detail. |
…nda-forge-pinning 2025.06.10.20.30.23
|
FWIW, I added running tests on osx and windows for upstream's github: and it seems was all green, so indeed might be worth ensuring we have for all OSes here. |
|
@conda-forge-admin, please rerender |
|
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 |
|
uff, we forgot about this one . @MattRs do you have juice to finish it up. I am afraid that is what causes datalad issues as well leading to attempts like @conda-forge-admin, please rerender |
|
still conflicts after rerendering??? that's odd... may be worth just to start from beginning for the PR -- I really do not get why this simple python package causes issues... 'no linux' was added in prehistoric times in commit 2042459 "py27 compatibility (#6)"... I will resubmit PR from clean state. |
Checklist
0(if the version changed)conda-smithy(Use the phrase@conda-forge-admin, please rerenderin a comment in this PR for automated rerendering)