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

Linter comment workflow breaks if the repo fork is renamed #29317

Open
freundTech opened this issue Feb 28, 2025 · 0 comments
Open

Linter comment workflow breaks if the repo fork is renamed #29317

freundTech opened this issue Feb 28, 2025 · 0 comments
Labels

Comments

@freundTech
Copy link
Contributor

Bug:

I just noticed that the make comment for staged-recipes linter workflow breaks when the head repository has been renamed.
In my case, I renamed my fork from freundTech/staged-recipes to freundTech/conda-forge-staged-recipes, but other users have also done so.
Here is an example of a failing workflow run.
The problem seems to be that the python script always assumes the head repo to be {args.head_repo_owner}/staged-recipes in line 44.

@conda-forge/staged-recipes

@freundTech freundTech added the bug label Feb 28, 2025
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