dsccommunity / dsccommunity/NetworkingDsc
chore: Improve GitHub issue templates to align with SqlServerDsc
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 235
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
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 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.ymlcontact links are still current
References
- SqlServerDsc ISSUE_TEMPLATE folder: https://github.com/dsccommunity/SqlServerDsc/tree/main/.github/ISSUE_TEMPLATE
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.
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.
Assessment
- Tech stack
- github
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100