Use GitHub Discussions for questions, how-to help, and general conversation about a project. Discussions are indexed by search engines, so your question and its answer may help future users.
To ask a question:
- Navigate to the repository for the specific module you need help with.
- Click Discussions → New discussion → choose the Q&A category.
- Search existing discussions first — your question may already be answered.
Use GitHub Issues for bugs: behavior that is clearly wrong, crashes, regressions, or documentation errors.
Before opening a bug:
- Check the existing issues (open and closed) for duplicates.
- Confirm you are using the latest release.
- Use the Bug Report issue template and fill it in completely.
Incomplete bug reports (missing version, no reproduction steps) will be asked to provide more information before investigation begins.
- Do not open a GitHub Issue to ask a how-to question. Issues are for tracked work, not support conversations. How-to issues will be redirected to Discussions.
- Do not email maintainers directly for support. Maintainers are volunteers; email bypasses the community who might also be able to help.
Do not report security vulnerabilities in public issues or discussions. See SECURITY.md for the responsible disclosure process.
Response times depend on the repository's lifecycle state. See CONTRIBUTING.md for current SLAs. PowerShellOrg projects are maintained by volunteers; we appreciate your patience.
If you have found a bug and want to fix it yourself, that is always welcome. See CONTRIBUTING.md to get started.