Skip to content

docs(community): add SECURITY policy, PR template, and YAML issue forms - #850

Merged
norrietaylor merged 1 commit into
mainfrom
pr/02-community-health
Jul 20, 2026
Merged

docs(community): add SECURITY policy, PR template, and YAML issue forms#850
norrietaylor merged 1 commit into
mainfrom
pr/02-community-health

Conversation

@norrietaylor

Copy link
Copy Markdown
Member

Second PR in the staged decomposition of oss/integration. Rounds out the community-health / governance surface.

What

  • SECURITY.md — private vulnerability disclosure via security@minimal.dev, acknowledgement/disclosure expectations, and what to include in a report.
  • .github/pull_request_template.md — a lightweight PR checklist.
  • Structured issue forms — replaces the free-form bug_report.md / feature_request.md markdown with GitHub issue forms (bug.yml, feature.yml) plus a config.yml.
  • CONTRIBUTING.md — fixes the TL;DR (a chanages typo and a 1-4-2-3 step ordering) and repoints the commit-message step at Conventional Commits (enforced by commitlint in CI).

Not included (already on main)

CODE_OF_CONDUCT.md, legal/ICLA.md, and legal/CCLA.md landed byte-identically via #836, so they're intentionally absent here.

Verification

  • All three issue-form YAMLs parse (yaml.safe_load).
  • Scanned the new public files: no invented emails or personal names, no leftover TODO/placeholder markers. security@minimal.dev is a role address on the project domain.

Independent of #848 (licensing) — reviewable in parallel.

🤖 Generated with Claude Code

Add SECURITY.md documenting private disclosure to security@minimal.dev, and
a pull request template. Replace the free-form markdown issue templates with
structured GitHub issue forms (bug.yml, feature.yml) and a config.yml.

Fix the CONTRIBUTING TL;DR — a typo and mis-ordered steps — and point the
commit-message step at Conventional Commits (enforced by commitlint in CI).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 31 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: d4d89954-b70b-4270-9200-95cba95b2992

📥 Commits

Reviewing files that changed from the base of the PR and between 8e54f90 and 14f9830.

📒 Files selected for processing (8)
  • .github/ISSUE_TEMPLATE/bug.yml
  • .github/ISSUE_TEMPLATE/bug_report.md
  • .github/ISSUE_TEMPLATE/config.yml
  • .github/ISSUE_TEMPLATE/feature.yml
  • .github/ISSUE_TEMPLATE/feature_request.md
  • .github/pull_request_template.md
  • CONTRIBUTING.md
  • SECURITY.md

Comment @coderabbitai help to get the list of available commands.

@norrietaylor
norrietaylor marked this pull request as ready for review July 20, 2026 21:16
@norrietaylor
norrietaylor merged commit c944727 into main Jul 20, 2026
27 of 28 checks passed
@norrietaylor
norrietaylor deleted the pr/02-community-health branch July 20, 2026 21:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants