Add bug_report template to the repository

[furkatgofurov7]

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.

[furkatgofurov7]

/triage accepted /good-first-issue

[metal3-io-bot]

@furkatgofurov7: This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-good-first-issue command.

In response to [this](https://github.com/metal3-io/metal3-dev-env/issues/1078): >/triage accepted >/good-first-issue Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[mquhuy]

/assign mquhuy

[Rozzii]

/help remove

[metal3-io-bot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[Rozzii]

@mquhuy what is up with this Issue, are you working on this or have you finished with this?

[mquhuy]

Oops. Sorry @Rozzii I completely forgot about this one. Will continue with it after the current work.

[metal3-io-bot]

Stale issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle stale.

/close

[metal3-io-bot]

@metal3-io-bot: Closing this issue.

In response to [this](https://github.com/metal3-io/metal3-dev-env/issues/1078#issuecomment-1435521614): >Stale issues close after 30d of inactivity. Reopen the issue with `/reopen`. Mark the issue as fresh with `/remove-lifecycle stale`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[furkatgofurov7]

/reopen

This is still needed

[metal3-io-bot]

@furkatgofurov7: Reopened this issue.

In response to [this](https://github.com/metal3-io/metal3-dev-env/issues/1078#issuecomment-1435645585): >/reopen > >This is still needed Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[Rozzii]

/remove-lifecycle stale

[harshithakolipaka]

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.

[furkatgofurov7]

@harshithakolipaka hi, sure!

/assign @harshithakolipaka

[harshithakolipaka]

hey @furkatgofurov7 , can you please check the above PR.

[metal3-io-bot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[Rozzii]

/close

[metal3-io-bot]

@Rozzii: Closing this issue.

In response to [this](https://github.com/metal3-io/metal3-dev-env/issues/1078#issuecomment-1580917323): >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[adilGhaffarDev]

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

[metal3-io-bot]

@adilGhaffarDev: Reopened this issue.

In response to [this](https://github.com/metal3-io/metal3-dev-env/issues/1078#issuecomment-2042315983): >somehow just stumbled on this issue. bug_template is still missing, it seems the fix was merged only fork not on the upstream. Reopening it. > >/reopen Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[Rozzii]

Thanks @adilGhaffarDev , nice catch!

[Rozzii]

/remove-lifecycle stale

[metal3-io-bot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[Rozzii]

/remove-lifecycle stale