weyne/dcs-retribution
1
0
Fork 0
mirror of https://github.com/dcs-retribution/dcs-retribution.git synced 2025-11-10 15:41:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated Developer's Guide (markdown)

MetalStormGhost 2022-07-23 13:49:52 +03:00
parent e5d3769635
commit ac6810623f
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Developer's-Guide.md

@ -124,6 +124,8 @@ The type checker is **not** run as part of pre-commit, since that makes it harde
Please make a new branch from either develop or master, and make your pull requests to khopa/develop.
We can only merge/revert whole PRs, which means you should try and keep the size of each individual PR as small as possible. Ideally, one PR for one feature/bugfix/change. Also, review latency doesn't scale linearly with review time, and review time doesn't scale linearly with PR complexity. **Smaller PRs will likely get reviewed sooner and faster.** In addition, it's not possible for the testers to isolate bugs on a sub-build level.
New features and bug fixes in pull requests are usually worth mentioning in the changelog. Exceptions are fixes for bugs that never shipped (were only present in a canary build), and changes with no intended user observable behavior, such as a refactor. If you're comfortable writing the note yourself, add it to `changelog.md` in the root of the project in the section for the upcoming release.
If you're new to GitHub, https://guides.github.com/introduction/flow/ and the other tutorials on that site may be helpful.