staged-recipes
staged-recipes copied to clipboard
added kedro-viz
Checklist
- [x] Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
- [x] License file is packaged (see here for an example).
- [x] Source is from official source.
- [x] Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
- [x] If static libraries are linked in, the license of the static library is packaged.
- [x] Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
- [x] Build number is 0.
- [x] A tarball (
url
) rather than a repo (e.g.git_url
) is used in your recipe (see here for more details). - [x] GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
- [x] When in trouble, please check our knowledge base documentation before pinging a team.
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 (recipes/kedro-viz
) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipes/kedro-viz:
- License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.
Documentation on acceptable licenses can be found here.
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 (recipes/kedro-viz
) and found it was in an excellent condition.
Fixed issue upstream (unnecessary dependency on test-requirements.txt in setup.py).
@conda-forge/help-python Is there an easy way to re-run CI after updating something upstream? (i.e. just got a dependency built with a new version)
You can go to the actions
tab and re-run. I just did that, but it's probably premature since it takes some time for the new version to hit the CDN. You can check https://conda-static.anaconda.org/conda-forge/rss.xml to see when the version you want appears.
Oops, checks
, not actions
.
@conda-forge-admin, please restart ci
Hi friend!
We really, really, really appreciate that you have taken the time to make a PR on conda-forge/staged-recipes
! conda-forge
only exists because people like you donate their time to build and maintain conda recipes for use by the community.
In an effort to maintain this repository and increase the signal-to-noise for open PRs, the maintainers of staged-recipes
close excessively old PRs after six months. This PR will remain open for another month, and then will be closed.
If you'd like to keep it open, please comment/push and we will be happy to oblige! Note that very old PRs will likely need to be rebased on main
so that they can be rebuilt with the most recent CI scripts. If you have any trouble, or we missed reviewing this PR in the first place (sorry!), feel free to ping the team using a special command in a comment on the PR to get the attention of the staged-recipes
team.
Cheers and thank you for contributing to this community effort!
Hi again! About a month ago, we commented on this PR saying it would be closed in another month if it was still inactive. It has been a month and so now it is being closed. Thank you so much for making it in the first place and contributing to the community project that is conda-forge
. If you'd like to reopen this PR, please feel free to do so at any time!
Cheers and have a great day!