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

Issue with valid repro is being closed #41

Closed
vanessayuenn opened this issue May 17, 2024 · 1 comment
Closed

Issue with valid repro is being closed #41

vanessayuenn opened this issue May 17, 2024 · 1 comment
Labels
bug Something isn't working invalid-reproduction

Comments

@vanessayuenn
Copy link

Link to reproduction

https://github.com/storybookjs/storybook

To reproduce

Thanks for introducing this tool in Storybook's repo! However, we're unable to get it working properly.
Please see this example issue, and our workflow config. We have to turn the bot off for now. For context, here is the log produced by the workflow (we have no reproduction-blocklist specified):

Link matched blocklist for reproduction URLs
Invalid reproduction, issue will be closed/labeled/commented/locked...
Issue #27188 closed/labaled/commented/locked. It does not contain a valid reproduction 😢

As an aside, is it possible to only comment + add a label on the issue without valid reproduction, and not close it? Our currently workflow is that we ask for repro, and wait 2 weeks before stale bot closes it.

Which area(s) are affected?

No response

@vanessayuenn vanessayuenn added the bug Something isn't working label May 17, 2024
Copy link

We could not detect a valid reproduction link. Make sure to follow the bug report template carefully.

Why was this issue closed?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We need a link to a public GitHub repository.

The bug template that you filled out has a section called "Link to reproduction", which is where you should provide the link to the reproduction.

  • If you did not provide a link or the link you provided is not valid, we will close the issue.
  • If you provide a link to a private repository, we will close the issue.
  • If you provide a link to a repository but not in the correct section, we will close the issue.

What should I do?

Depending on the reason the issue was closed, you can do the following:

  • If you did not provide a link, please open a new issue with a link to a reproduction.
  • If you provided a link to a private repository, please open a new issue with a link to a public repository.
  • If you provided a link to a repository but not in the correct section, please open a new issue with a link to a reproduction in the correct section.

In general, assume that we should not go through a lengthy onboarding process at your company code only to be able to verify an issue.

My repository is private and cannot make it public

In most cases, a private repo will not be a sufficient minimal reproduction, as this codebase might contain a lot of unrelated parts that would make our investigation take longer. Please do not make it public. Instead, create a new repository using the templates above, adding the relevant code to reproduce the issue. Common things to look out for:

  • Remove any code that is not related to the issue.
  • Remove any dependencies that are not related to the issue.
  • Remove any third-party service that would require us to sign up for an account to reproduce the issue.
  • Remove any environment variables that are not related to the issue.
  • Remove private packages that we do not have access to.
  • If the issue is not related to a monorepo specifically, try to reproduce the issue without a complex monorepo setup

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps by opening a new issue.

I think my reproduction is good enough, why aren't you looking into it quickly?

Sometimes we might miss one or two issues. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

Useful Resources

@github-actions github-actions bot locked and limited conversation to collaborators May 17, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working invalid-reproduction
Projects
None yet
Development

No branches or pull requests

1 participant