Project approval rules not inherited when creating an MR via the API
We do not have "Prevent editing approval rules in merge requests" checked, the only thing checked is "Prevent approval by author".
For API example, it's generally "lab mr create" at play -- https://zaquestion.github.io/lab/ -- but it's very sporadic whether or not it fails. Sometimes it seems that everything works fine, and then there are two slightly different manifestations of problems, if I'm thinking clearly. The first version is no approval rules present in the resulting MR at all. The second is the rule showing up, but having 0 required approvals, when the project default setting is 2 required approvals.
We do not have 'License-Check' or 'Coverage-Check' rules enabled at the project level. It's only our "All eligible users" rule, targeting all branches, with 2 approvals required.
Follow up issue from Inherit project-level approval rules on MR crea... (#13669 - closed)