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

Update PR template

Browse Source
This commit is contained in:
Raffson 2022-09-25 19:11:44 +02:00
parent 009574e8d5
commit ae0cbc2c5b
No known key found for this signature in database
GPG Key ID: B0402B2C9B764D99
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
.github/pull_request_template.md vendored
View File

@ -1,13 +1,14 @@
Pull requests should be made against the `develop` branch. Any backports Pull requests should be made against the `dev` branch. Any backports
necessary will be handled by the development team. necessary will be handled by the development team.
Pull requests should be focused on one task. Multiple bug fixes should be Pull requests should be focused on one task. Multiple bug fixes should be
multiple PRs. We cannot merge half a PR, and combined PRs are much more multiple PRs, or at the very least split over multiple (isolated) commits.
difficult to review. PRs that do not adhere to this will have their review We cannot merge half a PR, and combined PRs are more
difficult to review. PRs that do not adhere to this may have their review
delayed. delayed.
Prefer rebase to merge, and squash commits as needed to preserve a readable Prefer rebase to merge, and squash commits as needed to preserve a readable
commit history. This project maintains linear history in the develop branch, so commit history. This project maintains linear history in the `dev` branch, so
we will either rebase or squash your PR when merging. It is much easier for us we will either rebase or squash your PR when merging. It is much easier for us
if your branch already has a readable commit history (ensure that your commit if your branch already has a readable commit history (ensure that your commit
subject lines are clear enough to identify the patch in the git log). An subject lines are clear enough to identify the patch in the git log). An