GitHub PR template - merge strategies

[gerhardol]

Proposed changes

Add PR template section about merge strategy, setting squash merge as default.

Test methodology

Manual

Merge strategy

I agree that the maintainer squash merge this PR (if the commit message is clear).

---

✒️ I contribute this code under The Developer Certificate of Origin.

[RussKie]

The only problem I have with this - we'll have each PR with "1 of 4 tasks completed".

It looks like GitHub has a new syntax for handling dropdowns - have a look at https://github.com/dotnet/docs/blob/main/.github/ISSUE_TEMPLATE/breaking-change.yml

  - type: dropdown
    id: version
    attributes:
      label: Merge strategy
      description: How would you suggest to merge your changes?
      options:
        - Squash merge
        - Rebase merge
        - Merge
        - TBD

[gerhardol]

The only problem I have with this - we'll have each PR with "1 of 4 tasks completed".

It looks like GitHub has a new syntax for handling dropdowns - have a look at https://github.com/dotnet/docs/blob/main/.github/ISSUE_TEMPLATE/breaking-change.yml

Forms are not supported for PRs: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms

Will change to add a comment instead.