Update issue template

[mdevino]

Reopening as I just noticed #133 was closed.

This addresses #132.
Further discussion on what other relevant info might be needed is welcome.

[mdevino]

As requested here, I've updated the script to output as follows:

rustc 1.81.0 (eeb90cda1 2024-09-04)
Orchestrator version: 1.0.0 (279934c)

In case no tags are associated with the commit HEAD points to:

rustc 1.84.0 (9fc6b4312 2025-01-07)
Orchestrator version: No tag associated (1db5d59)

Does that work for you, @evaline-ju?

[declark1]

I closed the previous PR as it has been lingering open since July without being merged. Aren't bugs primarily reported through an internal channel? If users are using the released/versioned Dockerfile and code as-is for their deployments, it doesn't seem like details other than the release version would be needed for a bug report, i.e. they should not need to run a script?

Is the idea to also use this template for internal reporting and mirror bug reports here or have users open bug reports here directly going forward?

[mdevino]

Aren't bugs primarily reported through an internal channel?

Yes, but since this is an open-source project, I thought we wanted to make it easier for a developer working it to report bugs.

If users are using the released/versioned Dockerfile and code as-is for their deployments, it doesn't seem like details other than the release version would be needed for a bug report, i.e. they should not need to run a script?

In this case, yes, users would not need to run the script.

Is the idea to also use this template for internal reporting and mirror bug reports here or have users open bug reports here directly going forward?

I don't think so. I decided to update the bug report template when I was creating my first issues and thought the current template was too generic and not making much sense for our use case.

---

I'm okay with not merging this PR if we do not see any benefit in updating the template.