To propose a new feature to Pester or report a bug, we encourage you to first share your findings with us by creating a new issue. The feature or bug will be discussed, and if it's something we would like (or even love!) to see in our codebase we will ask you to create a pull request (PR) for it. We have a (more or less) standardized process for accepting PRs, but don't let that scare you away. We understand that you spent your free time to contribute, so we will take our time to help you successfully add your code to Pester.
Open source doesn’t always have the best reputation for being friendly and welcoming, and that makes us sad. Everyone belongs in open source, and Pester is dedicated to making you feel welcome.
We will never judge, condescend, or exclude anyone. Instead, we will go above and beyond to support the community, through helping you contribute to the Pester ecosystem, an open and inclusive code of conduct, and other means that empower and embrace the incredible community that makes Pester possible.
One of our community's values is that "you belong here".
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
The Pester community welcomes contributions. Please refer to the guides below on how to make sure your contributions get accepted:
For the latest news about Pester, follow @pspester on Twitter.