Investigate using config as code

[ewu63]

Description

We have too many repos, and managing their configs become difficult/time consuming. We should look into using probot/settings to store some centralized repository settings which can be shared across all the repos and keep everything in sync, especially for things like

• required status checks
• number of required review approvals
• enforce linear history

However, security/access becomes an issue so we have to be really careful about this. If someone gets write access to this file they can basically change the repo however they want. We may want to add extra protections or something.

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity.

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity.