Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
New submitters can't "ping @conda-forge/staged-recipes"
See original GitHub issueAccording to the README, “If your PR is passing all checks, but has not been acted on by the staged recipes maintainers for 1 week, you can ping @conda-forge/staged-recipes to request action.”, but non-members of theconda-forge organization can’t @mention @conda-forge/staged-recipes and new submitters aren’t invited to join conda-forge until after their feedstock has been accepted.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:7 (7 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The pull request template and/or linter bot’s message could explain what’s going on?
This has been fixed via the admin server hook: https://conda-forge.org/docs/maintainer/infrastructure.html#conda-forge-admin-please-ping-team