TST: Re-render bot

[jakirkham]

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 @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-linter]

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.

[jakirkham]

@conda-forge-admin, please re-render.

[github-actions]

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 tst_re-render
branch of jakirkham-feedstocks/zlib-feedstock. Did you check the "Allow edits from maintainers" box?

[jakirkham]

@beckermr, do you know why it can't push here? The error message the bot is giving doesn't seem correct as GitHub shows this line, "Add more commits by pushing to the tst_re-render branch on jakirkham-feedstocks/zlib-feedstock."

[isuruf]

Maybe github doesn't give the correct permissions for forks from organizations.

[jakirkham]

Are you able to push to this PR?

[isuruf]

Nope

[jakirkham]

Thanks for checking. Then yeah maybe there is something off with GitHub permissions here. FWIW I don't see the checkbox either.

[beckermr]

This is a known issue: conda-forge/conda-forge-webservices#288

I think this is how github intends it. Note they mention only user accounts in their docs: https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork