title: Is there a way to merge branches on GitHub via pull requests with different and enforced merge strategies?
body: <p>I have a very simple setup. A feature gets developed in a feature branch and then gets squash merged into <code>develop</code> and with enough features ready we want to do a merge commit to <code>master</code>. All of this should happen via pull requests. The idea behind this is to hide all the details of the individual commits that would end up in <code>develop</code>/<code>master</code> behind the feature itself.</p>
  
  <p>Currently, it seems not possible to actually enforce different merge types on different branches as described here: <a href="https://stackoverflow.com/questions/60076903/set-pull-request-merge-options-per-branch">Set pull request merge options per branch</a></p>
  
  <p>Even more importantly - is this actually a good strategy? Most of the people working with this are new to Git (including me) so I want to make this as easy and fail-safe as possible. I could not find any information on this after a googling for the last couple of hours.</p>
  
  <p>So, I guess my question is: What is an easy way or maybe the best way to set this up? Do others have the same problem? If so - how do they solve it? Or is this a question that stems solely from not understanding GitHub well enough?</p>
  
  <p>Any advice, documentation, or best practices you can point me too?</p>