chore: Improve GitHub issue templates to align with SqlServerDsc

Open Beginner friendly

#544 opened on Jun 21, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 72/100

Issue type: Documentation
Clarity: Mostly clear
Activity status: Quiet
Tech stack: github
Domain: documentation

Research direction

Start in .github/ISSUE_TEMPLATE/ and compare General.md, Resource_proposal.yml, and Problem_with_resource.yml with the corresponding SqlServerDsc templates. Check config.yml contact links as well. Done means the three files use the requested numeric names, their contents reflect the reference conventions, and the contact links remain current.

Written by the indexing model from the issue text.

Description

chore

Summary

Align the GitHub issue templates in this repository with the conventions used by SqlServerDsc, which serves as the reference implementation for DSC Community module issue templates.

Current state

The .github/ISSUE_TEMPLATE/ folder currently contains files without numeric prefixes, resulting in inconsistent ordering in the GitHub UI.

Desired state

Rename and align the existing files to match the SqlServerDsc naming convention (numeric prefixes ensure a consistent ordering in the GitHub UI):

Current file	New file	Action
`General.md`	`01_general.md`	Rename
`Resource_proposal.yml`	`02_resource_proposal.yml`	Rename
`Problem_with_resource.yml`	`03_problem_with_resource.yml`	Rename

Tasks

Rename General.md → 01_general.md
Rename Resource_proposal.yml → 02_resource_proposal.yml
Rename Problem_with_resource.yml → 03_problem_with_resource.yml
Review each template body against its SqlServerDsc counterpart and apply any improvements to wording, field labels, or descriptions
Verify config.yml contact links are still current

References

SqlServerDsc ISSUE_TEMPLATE folder: https://github.com/dsccommunity/SqlServerDsc/tree/main/.github/ISSUE_TEMPLATE

Dominant language: PowerShell
Stars: 235
Forks: 93
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

Gateway 3.16 Linux install: GPG key URL 404s (public_keys has no "316" entry, falls back to legacy key) Open

user-reported

Difficulty 2/5 1-3 hours Newbie friendliness 85/100

Kong/developer.konghq.com#7316 · Opened Sep 22, 2026
custom-resources teaches static verbs without the authorization obligation Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

HarperFast/skills#96 · Opened Sep 22, 2026
Client support matrix inclusion Open

enhancement

Difficulty 2/5 1-3 hours Newbie friendliness 68/100

modelcontextprotocol/ext-tasks#22 · Opened Sep 22, 2026
Document Hot Rod migration version compatibility for Data Grid 8.6 Open

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

infinispan/infinispan#18150 · Opened Sep 21, 2026
Typo in Dokumentation of Vue Component Open

Difficulty 1/5 Under an hour Newbie friendliness 78/100

fullcalendar/fullcalendar#8106 · Opened Sep 21, 2026