chore: Improve GitHub issue templates to align with SqlServerDsc
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- 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 content is aligned with the reference, and the links remain current.
Written by the indexing model from the issue text.
Description
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:
| File | Template name |
|---|---|
General.md |
General question or documentation update |
Resource_proposal.yml |
New resource proposal |
Problem_with_resource.yml |
Problem with a resource |
config.yml |
Blank issues disabled / contact links |
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.ymlcontact links are still current
References
- SqlServerDsc ISSUE_TEMPLATE folder: https://github.com/dsccommunity/SqlServerDsc/tree/main/.github/ISSUE_TEMPLATE
- Dominant language
- PowerShell
- Stars
- 338
- Forks
- 80
- PR merge metrics
- No merged PRs in 30d
Contributor 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.
More from dsccommunity/ComputerManagementDsc
-
chore
Difficulty 4/5 3-5 days Newbie friendliness 68/100
-
chore
Difficulty 4/5 3-5 days Newbie friendliness 64/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in dsccommunity/ComputerManagementDsc
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100