Question about github mechanisms for checking PR readiness before merge

There are various criteria that developers can choose among to prevent a PR from being merged before it is considered "ready".

One mechanism for enforcing the chosen criteria is the requirement of "status checks" to be successful before merging, see https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-status-checks-before-merging

Another mechanism is requiring a certain number of approved reviews before a PR can be merged, see https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-pull-request-reviews-before-merging

Question: does anyone think any of these mechanisms could be useful to the development of httomo?