Adds a bullet to the list of unacceptable behavior examples to indicate that unwanted communication outside of GitHub to draw attention to GitHub is a form of unacceptable behavior.

Cherry-pick auto-approval for release branches + standard human review fallback.

…sk#82)

The "standard human review" rule had no `if` conditions, causing
policy-bot to post a `pending` status on every PR across all installed
repos. Removing it so only cherry-pick PRs targeting release/* branches
are evaluated; all other PRs will get a "skipped" status.

Co-authored-by: Claude Opus 4.6 <[email protected]>

…ask#83)

When all rules have `if` conditions and none match, policy-bot posts
an error status ("All rules were skipped"). Adding a fallback rule
with no `if` and count:0 ensures non-matching PRs get a clean
"approved" status while cherry-pick PRs on release/* branches
continue to be evaluated by the targeted rule.

Co-authored-by: Claude Opus 4.6 <[email protected]>

…release (MetaMask#84)

Replace the blanket "no approval necessary" fallback with two scoped rules:

- "release branch review": requires release-team approval for all PRs
  targeting release/* branches that don't match cherry-pick criteria
- "non-release fallback": auto-approves PRs targeting non-release
  branches using RE2-compatible negation regex

This ensures PRs with wrong titles or large diffs on release branches
get PENDING status instead of being silently approved.

Co-authored-by: Claude Opus 4.6 <[email protected]>

…embers (MetaMask#85)

Without an author check, any external user could open a fork PR targeting
a release/* branch with "cherry-pick" in the title and fewer than 200 LOC,
causing policy-bot to post a passing status check.

Add `has_author_in: organizations: ["MetaMask"]` to the cherry-pick
auto-approval rule so the auto-approval path is only reachable by members
of the MetaMask GitHub organization.

Co-authored-by: Claude Sonnet 4.6 <[email protected]>

Co-authored-by: Claude Opus 4.6 <[email protected]>