dsccommunity / dsccommunity/ComputerManagementDsc

chore: Improve GitHub issue templates to align with SqlServerDsc

Open Beginner friendly
#463 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

chore
Dominant language
PowerShell
Stars
338
Forks
80
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:

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.md01_general.md
  • Rename Resource_proposal.yml02_resource_proposal.yml
  • Rename Problem_with_resource.yml03_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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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 content is aligned with the reference, and the 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
Clearly specified
Newbie friendliness
78/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.