The easier your PRs are to review and merge, the more likely your contribution will be accepted. :-)
- Work in a feature branch in a fork, PR to our master
- One logical change per PR, please - do refactorings in separate PRs, ahead of your feature change(s)
- Have editorconfig plugin for your editor(s) installed so that your file touches are consistent with ours and the diff is reduced.
- Test coverage should not go down
- Flag breaking changes in your PR description
- Add a comment linking to passing tests in CI, proof in Kibana dashboards ("share temporary"), etc
- Link to any specifications / JIRAs that you're working against if applicable
- CI should be green!
- CI should be green on master
- Bump the version number in CI - follow SemVer rules
- Bump the version in appveyor.yml to match
- Update the CHANGELOG.md
- Run
release.ps1
./release.ps1 -version 1.2.3
- CI should
- build the tag
- push nuget packages to nuget.org