-
Notifications
You must be signed in to change notification settings - Fork 119
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
Add bug_report template to the repository #1078
Comments
/triage accepted |
@furkatgofurov7: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign mquhuy |
/help remove |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
@mquhuy what is up with this Issue, are you working on this or have you finished with this? |
Oops. Sorry @Rozzii I completely forgot about this one. Will continue with it after the current work. |
Stale issues close after 30d of inactivity. Reopen the issue with /close |
@metal3-io-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/reopen This is still needed |
@furkatgofurov7: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/remove-lifecycle stale |
hey @furkatgofurov7 .. can you please assign this task to me .. I have already prepared a bug report template. I can add it immediately to this repository. |
@harshithakolipaka hi, sure! /assign @harshithakolipaka |
hey @furkatgofurov7 , can you please check the above PR. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/close |
@Rozzii: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
somehow just stumbled on this issue. bug_template is still missing, it seems the fix was merged only on the fork not on the upstream. Reopening it. /reopen |
@adilGhaffarDev: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Thanks @adilGhaffarDev , nice catch! |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
/lifecycle frozen |
It would be nice to have at least a template for bug report when creating an issue in the repo, since it is structured and requires needed information from the reporting person and in turn making it easier for maintainers or respondents of the issue to triage and debug the issue faster
You can check https://github.com/metal3-io/cluster-api-provider-metal3/tree/main/.github as a reference to find the template used in other repositories.
The text was updated successfully, but these errors were encountered: