Introducing protected branches

[mmikhasenko]

Proposal

A suggestion is to Introduce a protection to branch, once they are meaningful.
Let's define the latter as soon as the project reaches:

• at least one model Lc2pKpi.json
• at least one implementation of building, AmpForm or ThreeBodyDecaysIO.jl
• running CI with pages

Fully agree that reviews are manual cross check are extremely useful.
It's also a good habit to develop. Let's do it after the first project milestone.

Related conversation:

@mmikhasenko

Feel like review are not needed yet, at this stage. Do you mind turning it off?

@redeboer
Okay switched it off.
Reasons for turning it on are (1) to have more discussion and control over updates and (2) to reduce minor mistakes in the main branch by getting input from others first. Disadvantage may be that PRs that depend on each other would have to wait to be merged. (I don't think reviews slow down development overall: patching buggy commits takes time too and for some PRs a quick glance suffices.)