Identify core group of code reviewers, who approve commits to production

[HeatherAck]

No description provided.

[negillett]

@HeatherAck, will os-climate switch to a paid version of Github (team, enterprise)? Without that, branch protection for repos, which enforces approvals, CODEOWNER review, status checks, etc., before merging, isn't available, AFAIK.

The alternative is, I suppose, to just have limited Write, Maintain, Admin users to restrict use of push/merge to the repo.

cc @erikerlandson

[erikerlandson]

Our intent has been to make use of OWNERS, see for example:
https://github.com/operate-first/apps/blob/master/OWNERS

These are supposed to interact with sesheta bot, for example:
operate-first/apps#1556

That said, there are likely multiple benefits to switching to paid github acct, and I agree we should look into that

[erikerlandson]

cc @HumairAK @MichaelClifford

[HeatherAck]

os-climate switch to a paid version of Github (team, enterprise)? Without that, branch protection for repos, which enforces approvals, CODEOWNER review, status checks, etc., before merging, isn't available,

@negillett - I created a ticket with LF to upgrade. will keep you posted

[negillett]

Ah, interesting, @erikerlandson, thanks.

Yeah, GitHub repo branch protection offers quite a bit. A big one for me is forcing commits be submitted via pull requests.

[negillett]

It seems branch protection may be free for public repos. So, maybe we can wait until golive rather than upgrading the GitHub account, @HeatherAck.