Merge & Access Policy

[michaelcullum]

Merge policy. We can also implement https://pullapprove.com/ as a kind of soft-enforcement (doesn't affect pushing after all, just the green button).

@php-fig/secretaries

[samdark]

Not only in draft stage, I guess.

[michaelcullum]

We remove access to the main repo after the draft/review stage but leave the groups intact for @mentions

[michaelcullum]

Working to setup https://pullapprove.com

[michaelcullum]

@php-fig @php-fig/psr-5 @php-fig/psr-8 @php-fig/psr-9-10 @php-fig/psr-11 @php-fig/psr-12 @php-fig/psr-13 @php-fig/psr-14 @php-fig/psr-15 @php-fig/psr-16 @php-fig/psr-17

Apologies for the mass mention, it seemed like an easier way to get your attention as I think most of you missed the mailing list email. Could you all please review this policy (and +1 the first post for acknowledgement).

There is a sort of forced implementation of who can merge what on this repository by a tool called pull approve. Essentially, it requires one of the WG to approve modifications to a PSRs file by them just saying 👍 in the PR or hoping on the pull approve UI. Secretaries can override all of these approvals. You can see the config for who it will let approve (and therefore merge) what here.