-
-
Notifications
You must be signed in to change notification settings - Fork 228
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
Bug: Blog post highlights make up random repos #1995
Comments
Thanks for the issue, our team will look into it as soon as possible! If you would like to work on this issue, please wait for us to decide if it's ready. The issue will be ready to work on once we remove the "needs triage" label. To claim an issue that does not have the "needs triage" label, please leave a comment that says ".take". If you have any questions, please reach out to us on Discord or follow up on the issue itself. For full info on how to contribute, please check out our contributors guide. |
Although it's triage labeled, can I take it anyway? @bdougie |
We still need to triage it. We are trying to build a contributor culture where folks share an idea for the approach before we assign. We have had too many issues sit assigned with no response for months. With that said, can you look at the code make a suggestion for an approach? If you are on the @open-sauced/triage team, you are able to remove the label. |
Why is this happening: Currently, the repository is being tagged automatically based on the link given by the user. The way it can be fixed:
|
Thanks for exploring this @shamimbinnur. Assigned |
🎉 This issue has been resolved in version 1.73.0-beta.4 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 1.73.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Describe the bug
Steps to reproduce
The need for recognition is not a repo and every blog highlight should be linked to a repo.
The solution should enforce a repo being tagged on a blog highlight.
Browsers
Chrome
Additional context (Is this in dev or production?)
No response
Code of Conduct
Contributing Docs
The text was updated successfully, but these errors were encountered: