chore: add community health files and .gitattributes#6
Conversation
Closes #1. Raises the GitHub Community Profile now that the project is opening up to broader contribution: - SECURITY.md: private vulnerability reporting via GitHub Security Advisories, with a threat model centered on Arbella's core promise — no secret ever reaches the backup repo. - .github/ISSUE_TEMPLATE/: structured bug-report and feature-request forms (the feature form has a "tool to support" field, since Arbella adds tools as adapters), plus config.yml that disables blank issues and routes security reports to the advisory flow. - .github/PULL_REQUEST_TEMPLATE.md: a checklist covering typecheck/test/ build, cross-platform paths, and the secret-containment guarantee. Also adds .gitattributes (`* text=auto eol=lf`) so checkouts on a Windows filesystem or a WSL /mnt mount no longer flip every file to CRLF and produce whole-file diffs. This normalizes line endings going forward; a one-shot `git add --renormalize .` can clean existing churn separately. CONTRIBUTING.md is intentionally deferred per the issue's scope note.
|
Warning Review limit reached
More reviews will be available in 51 minutes and 4 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the 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 credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. 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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0dff79c1eb
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Closes #1.
What
Adds the public-repo community health files so the GitHub Community Profile is complete now that the project is opening up to broader contribution, plus a
.gitattributesto stop line-ending churn.SECURITY.md0600file, restore path-traversal, command injection)..github/ISSUE_TEMPLATE/bug_report.yml.github/ISSUE_TEMPLATE/feature_request.yml.github/ISSUE_TEMPLATE/config.yml.github/PULL_REQUEST_TEMPLATE.md.gitattributes* text=auto eol=lf— see below.Why
.gitattributesCheckouts on a Windows filesystem (including a WSL
/mntmount) currently flip every file to CRLF, producing whole-file diffs that bury real changes.* text=auto eol=lfnormalizes line endings to LF going forward;*.sh/install.share pinned LF and image assets are marked binary.This PR adds the file only — it does not renormalize existing files (that would balloon the diff into ~70 EOL-flip files). A one-shot
git add --renormalize . && git commitcan clean the existing churn in a separate, isolated commit whenever you want.Notes
CONTRIBUTING.mdis intentionally deferred per the issue's scope note ("optionally add later if outside contributors become relevant"). Happy to add a short one if you'd like it now.