Why "pullRequestAutoMerge" forces a squash merge?

[PSchwamborn-AINO]

I wanted to use the "pullRequestAutoMerge" property for our Update AL-Go System Files.
We have a lot of repositories and do not want to allow direct commits. So this setting is very useful for us.
Now I am wondering why this property forces a squash commit:
https://github.com/microsoft/AL-Go-Actions/blob/91d88b04dad77542fb8ac5a7a3cebee07e71952f/AL-Go-Helper.ps1#L1489
The problem is that we do not want to allow squash merged for our repositories. So, they are deactivated, and the action throws an error:

It's annoying that he created the pull request anyway, but I think that's a different issue...

So a new property that allows us to define the merge method would be very useful.
Or is there a specific reason why a squash merge is necessary here?

[aholstrup1]

Thanks for the feedback! I don't think there's any particular reason squash commits are needed so we could add a property to the settings that allows you to configure this

[aholstrup1]

I'm deploying a change to preview now that adds the ability to specify merge method. If you want to use it right away, please upgrade to preview and run Update AL-Go System Files to ensure you have the latest version. Otherwise, this feature will be shipped in next major/minor of AL-Go.

Details:
Now the commitOptions setting also includes a pullRequestMergeMethod setting that can be set to squash or merge. By default it is merge

https://aka.ms/algosettings#commitOptions