Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rerender command uses fork repo name as source of truth #557

Open
1 task done
jaimergp opened this issue May 25, 2023 · 0 comments
Open
1 task done

rerender command uses fork repo name as source of truth #557

jaimergp opened this issue May 25, 2023 · 0 comments
Labels

Comments

@jaimergp
Copy link
Member

Solution to issue cannot be found in the documentation.

  • I checked the documentation.

Issue

One of my forked feedstocks has a different name because it clashed with an existing repo. Instead of conda-libmamba-solver-feedstock, I renamed it to conda-libmamba-solver-conda-forge-feedstock.

I asked for a conda-forge-admin rerender and to my surprise the README included the fork repo name. See commit: conda-forge/conda-libmamba-solver-feedstock@5b21890

It sounds like conda-smithy is getting the repo name from the fork, not the target repo.

Installed packages

N/A

Environment info

N/A
@jaimergp jaimergp added the bug label May 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

1 participant