Merge strategy policy settings inconsistent

[aguacongas]

If we protect a branch with Enforce a merge strategy policy and we call the Evaluations - List api, the policy.configuration.settings object returned is not the same on TFS 2018 tha Azure DevOps Services:

• On TFS 2018 the settings property contains a useSquashMerge property setted to true when we force Squash merge

  "settings": {
  "useSquashMerge": true
  }

  or false when we force Not-fast-forward merge

  "settings": {
  "useSquashMerge": false
  }

• On Azure DevOps Services the settings property contains an allowSquash property setted to true when we force Squash merge

  "settings": {
  "allowSquash": true
  }

  or an allowNoFastForward property setted to true when we force Not-fast-forward merge

  "settings": {
  "allowNoFastForward": true
  }

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 00030517-ac2e-341b-3c81-8b834758eca1
• Version Independent ID: 5b536189-1e4d-f097-3a83-24998b65f928
• Content: Evaluations (Azure DevOps Policy)
• Content Source: docs-ref-autogen/5.0/policy/Evaluations.yml
• Product: devops
• Technology: devops-ref
• GitHub Login: @wnjenkin
• Microsoft Alias: whjenkin

[milind009]

Any update on this? I also faced this issue while getting the policy configurations of a particular branch