You do not need a large project or a perfect first draft. Share something useful, explain how you tested it, and help the next person start a little further ahead.
Pick a contribution that fits
| If you have... | You could... |
|---|---|
| A script that saves you time | Create a new sample with its scenario, prerequisites, and expected result. |
| A different preferred tool | Add an implementation to an existing sample, such as Microsoft Graph PowerShell or CLI for Microsoft 365. |
| A few minutes | Fix a typo, clarify a permission, improve alt text, or replace an outdated screenshot. |
| A reproducible problem | Open an issue with the sample name, tool version, and redacted steps. |
| A scenario you cannot find | Search the gallery, then suggest it in an issue. Include the outcome you need, not private tenant data. |
| Experience to share | Help test a contribution, review guidance, or demo a sample on a community call. |
For larger ideas, open an issue first so others can offer feedback or collaborate. You do not need an issue before fixing a typo.
Make your script a useful starting point
- Describe what it does, when it helps, and what the reader should expect.
- Include at least one tested implementation, required tools, and authentication/permission guidance.
- Use clear names and readable formatting. Add comments where the intent is not obvious.
- Replace credentials, usernames, IDs, and tenant-specific addresses with safe placeholders.
- Put a clear impact warning before commands that modify or remove data. Test safely and explain your test environment.
- Credit everyone who helped. Keep metadata, tool versions, and the preview consistent with the README.
The sample preparation guide has the generator command and checklist. No website-development experience is needed.
Keep your pull request focused
Fork the repository and work on a branch. Keep a sample and its related documentation or images in one pull request; separate unrelated changes so they are easier to review.
For an existing sample, edit its files directly. Do not rerun the new-sample generator over it. Add yourself alongside the existing authors when you make a meaningful contribution, and describe the changes in the pull request.
See submitting a pull request for the review process. If GitHub is new to you, Sharing is caring can help.
Help your contribution reach others
Once published, share the sample's gallery link, credit its authors, and describe the problem it solves. A short post, a team demo, or a helpful answer linking to the sample can make a difference.
Every sample contributor is eligible for the Script Samples contributor badge. After your first accepted sample, opt in to the recognition program.
