Add issue templates
Metadata
Current evaluation
Closed without implementation after discussion of generic templates or post-creation generation; linked examples were craft-application#37 and charmcraft#1106.
Resolution: closed stale
Reason: The sole follow-up proposed generic templates or a README/script-based setup, and no resolving PR or commit was identified before the issue was closed.
Evaluated by: mr-cal-bot
No scores available.
Issue body
We should have GitHub issue templates following the new templates. However, this differs for applications and libraries, so we'd need to consider how to do so as well.
* Library example: https://github.com/canonical/craft-application/pull/37
* Application example: https://github.com/canonical/charmcraft/pull/1106
Marking this as help wanted because I don't immediately have a good way to do it. Notably the bug template is quite different. I'd love to hear ideas from anyone who might have them, as currently the best I have is to use the library template for now (which would be an appropriate template for starbase itself) and include the application template elsewhere with documentation about updating it if we want to use it.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | Closed without implementation after discussion of generic templates or post-creation generation; linked examples were craft-application#37 and charmcraft#1106. | |
| stealth/space-bunny-alpha | — | closed stale | Closed without implementation after discussion of generic templates or a post-creation generation script; no resolving PR or commit was identified. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. A contributor suggested using generic issue templates or a post-creation generation script to standardize templates across repositories. | |
| qwen/qwen3.6-35b-a3b | — | — | The issue requesting GitHub issue templates was closed. A contributor proposed using generic templates or a script to generate them after repository creation, addressing the need to differentiate between libraries and applications. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/craft-application#37
(confidence 100%)
Cited as an example of library issue templates, but did not resolve starbase#112.
-
Related To:
canonical/charmcraft#1106
(confidence 100%)
Cited as an example of application issue templates, but did not resolve starbase#112.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #78 Add issue templates | imagecraft | closed | Issue templates for task/bug/spike types were added to imagecraft and closed by merged PR #79 (commit 53008e0, merge commit 6e3cee1). Later refined in #236 and #281. |