- Update contribution guidelines to make updating the changelog required
- add a checklist to PR template
Comment by @SteveL-MSFT :
> Everyone should understand that we are always open to feedback and nothing is set in stone. Based on a team discussion, one of the biggest costs for a release is creating the ChangeLog hence updating this document to push it to the contributor most aware of why the changes are being made and ideally how it's useful to end users.
* Update coding guidelines to make it more concrete and useful in a review process.
* Add a section about security
* Address comments
* Update .spelling
* Address more comments
* Address comment about the security section
* Fix 'i.e.' and 'e.g.'
* Update .spelling
* One more tweak
* Add motivation for using 'nameof'
Update pull-request-process to clarify role/responsibility of author and reviewers based on recent feedback from team and community. Also moved it to `.github/CONTRIBUTING.md` so that all related information can be found at one place.
* Remove PR template, update guidelines for PR
* Update testing-guidelines.md
* Add clarification on when to use runtime/compiletime checks
* Update issue label descriptions
Now that we've gotten enough of a sign-off
from everyone involved in the governance
process, the docs need to be reworked to use a
consistent terminology set, links, and directory
structure.
* Links fixed.
* Link to maintainers removed; superfluous in this document.
* TODO added to changelog.
(I don't like this but was hesitant to remove it).
* Periods and spelling fixed.
Rework of contributor docs to reflect actual flow
for both internal and external developers using
the PowerShell/PowerShell repo for the first time.
Includes updates to issue/PR guidelines, repo 101,
and CONTRIBUTING.md.
