Alternative to #3 - Githubissues

jamesmyatt commented 3 years ago

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

conda-forge-linter commented 3 years ago

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.

jamesmyatt commented 3 years ago

@conda-forge-admin, please rerender

github-actions[bot] commented 3 years ago

Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like I wasn't able to push to the global_install branch of jamesmyatt/vega-cli-feedstock. Did you check the "Allow edits from maintainers" box?

jamesmyatt commented 3 years ago

@conda-forge-admin, please rerender

github-actions[bot] commented 3 years ago

Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like I wasn't able to push to the global_install branch of jamesmyatt/vega-cli-feedstock. Did you check the "Allow edits from maintainers" box?

jamesmyatt commented 3 years ago

Closed this because I can't get the conda-forge bot to access my branch

conda-forge / vega-cli-feedstock

Alternative to #3 #5