Add community health files, issue templates, and CI workflows for better project management. #2
Conversation
…ter project management.
📝 WalkthroughSummary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings. WalkthroughThis PR introduces GitHub repository infrastructure and community governance. It adds sponsor metadata, standardized issue templates for bug reports and feature requests, a linter workflow, an expanded .gitignore, a code of conduct, and a pull request template to establish project standards. Changes
Possibly related PRs
Poem
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 📜 Recent review detailsConfiguration used: Organization UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
✏️ Tip: You can disable this entire section by setting 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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In @.github/ISSUE_TEMPLATE/bug-report.yml:
- Around line 2-3: Update the description field in
.github/ISSUE_TEMPLATE/bug-report.yml to include the missing article by changing
"Let us know about problem" to "Let us know about the problem" so the sentence
reads correctly; edit the value of the YAML key description in the file to apply
this grammar fix.
🧹 Nitpick comments (1)
CODE_OF_CONDUCT.md (1)
43-48: Consider adding a contact method for reporting violations.The enforcement section mentions contacting "core team members" but doesn't specify how (email address, form, etc.). Adding a concrete contact method improves actionability for reporters.
💡 Suggested improvement
## Enforcement -Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting core team members. All +Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the core team at [conduct@example.com or via GitHub issues]. All complaints will be reviewed and investigated promptly and fairly.
📜 Review details
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (8)
.github/FUNDING.yml.github/ISSUE_TEMPLATE/bug-report.yml.github/ISSUE_TEMPLATE/feature-request.yml.github/workflows/linter.yml.gitignoreCENTRALIZING_GITHUB_ORGANIZATION_CONFIGURATION.mdCODE_OF_CONDUCT.mdPULL_REQUEST_TEMPLATE.md
🧰 Additional context used
🧠 Learnings (4)
📓 Common learnings
Learnt from: terabytesoftw
Repo: php-forge/support PR: 12
File: src/TestSupport.php:0-0
Timestamp: 2025-08-18T20:13:33.518Z
Learning: User terabytesoftw prefers clean trait-based designs over maintaining backward compatibility wrappers when refactoring utility classes in the php-forge/support project.
Learnt from: terabytesoftw
Repo: php-forge/actions PR: 65
File: .github/workflows/composer-require-checker.yml:80-83
Timestamp: 2025-09-28T15:12:48.345Z
Learning: The user terabytesoftw prefers using floating tags like v1 for third-party actions in GitHub workflows instead of pinning to specific commit SHAs, even when it's a security best practice to pin to immutable commits.
📚 Learning: 2025-09-28T15:12:48.345Z
Learnt from: terabytesoftw
Repo: php-forge/actions PR: 65
File: .github/workflows/composer-require-checker.yml:80-83
Timestamp: 2025-09-28T15:12:48.345Z
Learning: The user terabytesoftw prefers using floating tags like v1 for third-party actions in GitHub workflows instead of pinning to specific commit SHAs, even when it's a security best practice to pin to immutable commits.
Applied to files:
.github/FUNDING.yml
📚 Learning: 2025-09-12T10:52:52.955Z
Learnt from: terabytesoftw
Repo: php-forge/actions PR: 55
File: .github/workflows/reusable/linter.yml:65-79
Timestamp: 2025-09-12T10:52:52.955Z
Learning: For Super Linter workflows, always recommend using the official super-linter/super-linter action instead of docker run commands, as the action properly handles GitHub context variables and annotations automatically.
Applied to files:
.github/workflows/linter.yml
📚 Learning: 2025-09-12T13:21:35.231Z
Learnt from: terabytesoftw
Repo: php-forge/actions PR: 56
File: .github/workflows/linter.yml:19-21
Timestamp: 2025-09-12T13:21:35.231Z
Learning: In GitHub Actions, when a reusable workflow defines its own permissions block, those permissions are sufficient for the actions within that reusable workflow. The caller workflow does not need to grant additional permissions if the reusable workflow already has the necessary permissions defined.
Applied to files:
.github/workflows/linter.yml
🪛 LanguageTool
CODE_OF_CONDUCT.md
[style] ~5-~5: Consider a more concise word here.
Context: ...rs and maintainers of this project, and in order to keep community open and welcoming, we a...
(IN_ORDER_TO_PREMIUM)
[style] ~21-~21: Try using a synonym here to strengthen your wording.
Context: ...ind - Trolling, insulting or derogatory comments, and personal or political attacks - Pu...
(COMMENT_REMARK)
CENTRALIZING_GITHUB_ORGANIZATION_CONFIGURATION.md
[uncategorized] ~7-~7: The official name of this software platform is spelled with a capital “H”.
Context: ...ub organization configuration using the .github repository pattern, drawing from real-...
(GITHUB)
[uncategorized] ~9-~9: The official name of this software platform is spelled with a capital “H”.
Context: ...rience across all repositories. ## The .github Repository Pattern At the heart of Gi...
(GITHUB)
[uncategorized] ~11-~11: The official name of this software platform is spelled with a capital “H”.
Context: ...guration lies a special repository: the .github repository. When created as a public r...
(GITHUB)
[uncategorized] ~22-~22: The official name of this software platform is spelled with a capital “H”.
Context: ... Repository Structure A well-organized .github repository typically includes: ```yam...
(GITHUB)
[uncategorized] ~62-~62: The official name of this software platform is spelled with a capital “H”.
Context: ...e files in this order: 1. Repository's .github/ folder 2. Repository root directory 3...
(GITHUB)
[uncategorized] ~65-~65: The official name of this software platform is spelled with a capital “H”.
Context: ...folder 4. Default from organization's.github` repository This hierarchy allows repo...
(GITHUB)
[uncategorized] ~169-~169: The official name of this software platform is spelled with a capital “H”.
Context: ...usable workflows there: org/actions/.github/workflows/super-linter.yml: YAML exa...
(GITHUB)
[uncategorized] ~464-~464: The official name of this software platform is spelled with a capital “H”.
Context: ...## Phase 1: Foundation 1. Create the .github repository ```bash # Create as...
(GITHUB)
[uncategorized] ~534-~534: The official name of this software platform is spelled with a capital “H”.
Context: ...nization documentation** - README in .github repository - Contribution guideline...
(GITHUB)
[uncategorized] ~585-~585: The official name of this software platform is spelled with a capital “H”.
Context: ...ege ## Common Pitfalls ### 1. Private .github Repository The .github repository m...
(GITHUB)
[uncategorized] ~587-~587: The official name of this software platform is spelled with a capital “H”.
Context: ...## 1. Private .github Repository The .github repository must be public for template...
(GITHUB)
[uncategorized] ~607-~607: The official name of this software platform is spelled with a capital “H”.
Context: ... organization configuration through the .github repository pattern provides significan...
(GITHUB)
[uncategorized] ~624-~624: The official name of this software platform is spelled with a capital “H”.
Context: ...## Example Repositories - ui-awesome/.github...
(GITHUB)
[uncategorized] ~625-~625: The official name of this software platform is spelled with a capital “H”.
Context: ...ete implementation example - [GitHub's .github repository](https://github.com/github/....
(GITHUB)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: linter / Super Linter
- GitHub Check: linter / Super Linter
🔇 Additional comments (8)
.github/FUNDING.yml (1)
1-2: LGTM!The funding configuration is correctly formatted and will enable the GitHub Sponsors button on the repository.
PULL_REQUEST_TEMPLATE.md (1)
1-8: LGTM!Clean and concise PR template with essential fields for tracking bugfixes, features, breaking changes, and related issues.
.github/workflows/linter.yml (1)
13-17: Verify the reusable workflow source organization.The workflow references
yii2-framework/actionsbut this PR is for thephp-forgeorganization. Confirm this is intentional and that theyii2-framework/actionsrepository provides the appropriate super-linter configuration for php-forge projects.Based on learnings, the use of floating tag
@v1and the defined permissions align with user preferences..github/ISSUE_TEMPLATE/feature-request.yml (1)
1-11: LGTM!Minimal and effective feature request template with required description field. The template enforces users to provide context about proposed features.
CODE_OF_CONDUCT.md (1)
87-102: LGTM!Proper attribution to Contributor Covenant v2.1 with correctly formatted reference links.
.github/ISSUE_TEMPLATE/bug-report.yml (1)
4-31: LGTM!Well-structured bug report template with:
- Security advisory warning redirecting vulnerability reports appropriately
- Required fields for description, package version, and PHP version
- Helpful placeholders and descriptions guiding users
.gitignore (1)
1-51: Looks good for repo hygiene.Covers the usual OS, IDE, PHP, and Node artifacts without introducing risky ignores.
CENTRALIZING_GITHUB_ORGANIZATION_CONFIGURATION.md (1)
1-632: Strong, comprehensive guide.The structure and examples are clear, consistent, and actionable for org-wide standardization.
✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.
No description provided.