chore: normalize LICENSE copyright to Passion Factory and add community-health files#290
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 3 minutes 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 (9)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
![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 essential community and contribution documents, including issue and pull request templates, a code of conduct, contributing guidelines, and a security policy, alongside updating the license copyright. The review feedback identifies two key inconsistencies: the contribution guide's English-only policy conflicts with the project's actual support for Korean documentation, and the pull request template checklist lacks the type-check and build verification steps described in the development workflow.
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.
Greptile SummaryThis is a documentation-only PR that normalizes the LICENSE copyright holder from "PleaseAI" to "Passion Factory" and adds the standard set of open-source community-health files.
Confidence Score: 5/5All changes are documentation and governance files with no effect on runtime code. No code is modified — only the LICENSE copyright name, markdown docs, and GitHub template files are touched. All script names referenced in CONTRIBUTING.md and the PR template match the actual scripts in package.json. Contact addresses and external links are consistent across files. No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Contributor] -->|Opens issue| B{Issue type?}
B -->|Bug| C[bug_report.md - label: bug]
B -->|Feature| D[feature_request.md - label: enhancement]
B -->|Question| E[GitHub Discussions]
B -->|Security| F[GitHub Private Advisory]
F --> G[security at pleaseai.dev fallback]
A -->|Opens PR| H[PULL_REQUEST_TEMPLATE.md]
H --> I{CI passes?}
I -->|Yes| J[Request review]
I -->|No| K[Fix and re-push]
K --> I
A -->|Conduct concern| L[CODE_OF_CONDUCT.md enforcement]
%%{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] -->|Opens issue| B{Issue type?}
B -->|Bug| C[bug_report.md - label: bug]
B -->|Feature| D[feature_request.md - label: enhancement]
B -->|Question| E[GitHub Discussions]
B -->|Security| F[GitHub Private Advisory]
F --> G[security at pleaseai.dev fallback]
A -->|Opens PR| H[PULL_REQUEST_TEMPLATE.md]
H --> I{CI passes?}
I -->|Yes| J[Request review]
I -->|No| K[Fix and re-push]
K --> I
A -->|Conduct concern| L[CODE_OF_CONDUCT.md enforcement]
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.
3 issues found across 9 files
Confidence score: 4/5
- The highest risk is in
CONTRIBUTING.md: telling contributors to runbun run lintinstead ofbun run lint:fixcan lead to avoidable lint failures and extra review churn when changes are pushed without auto-fixes — update the workflow step to the required command before merging. .github/PULL_REQUEST_TEMPLATE.mdis missingbun run type-checkandbun run build, so PRs may be marked ready while still failing CI on checks the team expects — add both checklist items to align contributor behavior with the documented process.- The wording in
CONTRIBUTING.mdaround language policy is overly absolute and could confuse contributors about whether maintained translations are acceptable — revise it to state English as the default while explicitly allowing supported translations.
Architecture diagram
sequenceDiagram
participant C as Contributor / Researcher
participant GH as GitHub Repository
participant T as Issue Templates
participant S as Security Policy
participant M as Maintainers
Note over C,M: NEW: Community-Health Files establish contributor & security flows
C->>GH: Visits repo, sees LICENSE badge & Code of Conduct link
C->>GH: Reads CONTRIBUTING.md (clone, bun install, lint/test/build)
C->>GH: Opens a new issue
GH->>T: Presents bug_report.md or feature_request.md
alt Bug report
T-->>C: Form fields (describe bug, reproduce, environment)
C->>GH: Submits issue
GH->>M: Notifies maintainers
else Feature request
T-->>C: Form fields (problem, solution, alternatives)
C->>GH: Submits issue
GH->>M: Notifies maintainers
end
opt Security vulnerability
S-->>C: Redirects to private reporting (Security tab / security@pleaseai.dev)
C->>S: Follows instructions (not public issue)
S->>M: Private report received
M-->>C: Acknowledges within 72h
end
C->>GH: Opens pull request
GH->>C: Shows PR template (checklist, Conventional Commits)
C->>GH: Submits PR
GH->>M: Notifies maintainers
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
|
✅ @amondnet님의 요청을 완료했습니다 (2m 20s) —— View job PR Review
AssessmentThis is a clean docs-only PR. All three automated reviewers' feedback has been addressed in commit
On
|
1 participant
Summary
Normalizes the LICENSE copyright holder and adds the standard open-source community-health files.
LICENSE: copyright holderPleaseAI->Passion Factory(year 2025 unchanged)CONTRIBUTING.md: bun-based setup and workflow (clone,bun install,bun run lint/type-check/test/build)CODE_OF_CONDUCT.md: Contributor Covenant v2.1, contactconduct@pleaseai.devSECURITY.md: private vulnerability reporting, contactsecurity@pleaseai.dev.github/PULL_REQUEST_TEMPLATE.md.github/ISSUE_TEMPLATE/:bug_report.md,feature_request.md,config.ymlREADME.md: added aLicense: MITbadge to the badge row (an npm version badge was already present, so no npm badge was added to avoid a duplicate)Related issue
Checklist
Summary by cubic
Normalize LICENSE holder to Passion Factory and add community health files to guide contributions, conduct, and security. Includes Contributor Covenant v2.1 (conduct@pleaseai.dev), SECURITY policy with private reporting via GitHub advisories or security@pleaseai.dev, CONTRIBUTING with Bun workflow, PR/issue templates that link to Discussions and disable blank issues, and an MIT license badge in the README.
Written for commit d217beb. Summary will update on new commits.