chore: normalize LICENSE copyright to Passion Factory and add community-health files#70
Conversation
|
Warning Review limit reached
Next review available in: 1 minute Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?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 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (8)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces community and repository configuration files, including issue and pull request templates, contributing guidelines, a code of conduct, and a security policy, alongside updating the copyright holder in the license. The review feedback correctly identifies an inconsistency in the pull request template, where the checklist commands (bun run) do not align with the mise run commands recommended in CONTRIBUTING.md.
Not up to standards ⛔🔴 Issues
|
| Category | Results |
|---|---|
| Security | 1 high |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Greptile SummaryThis PR normalizes the LICENSE copyright holder from
Confidence Score: 5/5Safe to merge — all changes are documentation and community-health files; no code, build, or runtime behavior is affected. The only functional change is a one-line copyright string update in LICENSE. All new files are documentation: the mise tasks and cargo commands in CONTRIBUTING.md were verified against the actual mise.toml and package.json. No logic, APIs, or dependencies are touched. No files require special attention. The minor checklist inconsistency in Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Contributor] -->|clone + mise install + bun install| B[Dev Environment]
B --> C{Type of change}
C -->|JS/TS| D[mise run lint\nmise run typecheck]
C -->|Rust| E[cargo fmt --all\ncargo clippy]
C -->|Both| F[mise run check\nfull gate]
D --> G[Open PR]
E --> G
F --> G
G -->|uses| H[.github/PULL_REQUEST_TEMPLATE.md]
H --> I[CI green?]
I -->|No| B
I -->|Yes| J[Request review]
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
A[Contributor] -->|clone + mise install + bun install| B[Dev Environment]
B --> C{Type of change}
C -->|JS/TS| D[mise run lint\nmise run typecheck]
C -->|Rust| E[cargo fmt --all\ncargo clippy]
C -->|Both| F[mise run check\nfull gate]
D --> G[Open PR]
E --> G
F --> G
G -->|uses| H[.github/PULL_REQUEST_TEMPLATE.md]
H --> I[CI green?]
I -->|No| B
I -->|Yes| J[Request review]
Reviews (2): Last reviewed commit: "chore: apply AI code review suggestions" | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
1 issue found across 8 files
Architecture diagram
sequenceDiagram
participant C as Contributor
participant GH as GitHub
participant Repo as code-search Repo
participant Maintainer as Maintainers
participant Security as Security Team
Note over C,Security: Community Health Files – Interaction Flows
C->>GH: Visits repository
GH->>C: Shows README, LICENSE (Passion Factory), CONTRIBUTING.md, etc.
C->>Repo: Reads CONTRIBUTING.md
Repo->>C: Provides setup instructions: mise, bun install, cargo
C->>C: Follows workflow: create branch, run lint/typecheck/test/check
alt Reports a bug
C->>GH: Opens issue via bug_report.md template
GH->>Repo: Creates issue with labels ["bug"]
Repo->>Maintainer: Notifies maintainers
else Requests a feature
C->>GH: Opens issue via feature_request.md template
GH->>Repo: Creates issue with labels ["enhancement"]
Repo->>Maintainer: Notifies maintainers
else Submits a PR
C->>GH: Opens pull request using PULL_REQUEST_TEMPLATE.md
GH->>Repo: Creates PR with checklist (Conventional Commits, tests, lint, docs)
Repo->>Maintainer: Requests review
Maintainer->>C: Provides feedback / approves
C->>GH: Updates PR until CI green
Maintainer->>GH: Merges squash-commit
end
alt Reports a security vulnerability
C->>GH: Navigates to Security tab -> "Report a vulnerability"
GH-->>Security: Creates private advisory
Security->>C: Acknowledges within 72 hours
Security->>Security: Investigates and prepares fix
Security->>GH: Publishes advisory + credit (optional)
end
Note over C,Maintainer: Code of Conduct enforced via conduct@pleaseai.dev
C->>Maintainer: (if incident) Reports via conduct@pleaseai.dev
Maintainer->>C: Investigates and applies enforcement guidelines
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
|
1 participant
Summary
Normalizes the LICENSE copyright holder and adds the standard open-source community-health files (all previously missing).
Copyright (c) 2026 pleaseai→Copyright (c) 2026 Passion Factory(year unchanged).bun installfor JS,cargofor Rust — withmise run lint|typecheck|test|checkas the dev workflow.conduct@pleaseai.dev.security@pleaseai.dev.bug_report.md,feature_request.md,config.yml(discussions + security advisory links point topleaseai/code-search).README already carries a License badge and 6 others, so it is left unchanged.
Related issue
None.
Checklist
Summary by cubic
Normalize the LICENSE holder to Passion Factory and add standard community-health files to formalize contribution, conduct, and security processes. This improves governance and gives contributors clear guidance.
mise(node,bun,hk),bun install, Rust viacargo, andmise run lint|typecheck|test|check.Written for commit e0267e6. Summary will update on new commits.