PoC: Use of rules to protect SCM branches

[sourabhsparkala]

We can enforce certain workflows or requirements before a collaborator can push changes to a branch in our repository, including merging a pull request into the branch, by creating a branch protection rule.

By default, each branch protection rule disables force pushes to the matching branches and prevents the matching branches from being deleted. We can optionally disable these restrictions and enable additional branch protection settings.

We can maybe check these settings' configurations to harness some quantifiable value.

There are settings that can be enabled or disabled. https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-settings

Ref: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches

Things to do:

• Check if a new feature can be used in the rating core.
• Check if a new score using the feature that can be introduced.