[Proposal] make "master" a protected branch to enforce update via PRs only

[mi-hol]

I'd recommend to enforce certain workflows for "master" branch via "protection rules"- Possible "protection rules" such as requiring an approving review or passing status checks for all pull requests merged into the protected branch.
How to is documented in (https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)

Background:
every member of doc-team has "merge" permission and can push to "master" branch unintentionally.

[mi-hol]

this change links nicely with #244 & #308

[mi-hol]

Andrey is fine with recommendation provided by doc-team

[chuckwagoncomputing]

I've already spoken to @mi-hol about this, but just so everyone is on the same page:
This will also mean disabling editing from https://github.com/rusefi/rusefi/wiki

[rusefillc]

[rusefillc]

even with branch protection I can still make direct commits a895791

to be honest that works for me

[rusefillc]

I've already spoken to @mi-hol about this, but just so everyone is on the same page: This will also mean disabling editing from https://github.com/rusefi/rusefi/wiki

at the moment exactly one person can edit https://github.com/rusefi/rusefi/wiki directly and that's me

please clarify the thought process here, what are we trying to solve how?

[chuckwagoncomputing]

As I understand it, the goal is to keep people from making bad commits that someone has to fix later.

Just to confirm, have you also selected "Require status checks to pass before merging"?

[rusefillc]

I did now

[chuckwagoncomputing]

OK Thanks.

[mi-hol]

Thank you all, from my view this is a great process improvement!