Add funding, issue templates, linter configuration, and code of conduct.#4
Add funding, issue templates, linter configuration, and code of conduct.#4terabytesoftw merged 2 commits intomainfrom
Conversation
📝 WalkthroughWalkthroughThis PR adds comprehensive repository infrastructure and documentation setup. It introduces GitHub funding configuration, issue templates for bug reports and feature requests, a linter workflow, a Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 📜 Recent review detailsConfiguration used: defaults 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)
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/linters/actionlint.yml:
- Around line 4-7: Remove the three actionlint ignore entries that suppress the
messages '"pull_request" section is alias node but mapping node is expected',
'"push" section is alias node but mapping node is expected', and 'section is
alias node but mapping node is expected' unless you have a documented
false-positive from a specific actionlint version; to fix, delete those lines
from the ignore list (or replace them with a short comment documenting the exact
actionlint version and workflow file that produced the false positive), and
ensure any remaining suppressions explicitly reference the exact workflow
filename and actionlint version that necessitates them.
🧹 Nitpick comments (1)
CODE_OF_CONDUCT.md (1)
5-5: Optional: Consider simplifying phrasing.The phrase "in order to" could be shortened to "to" for conciseness.
📝 Suggested simplification
-As contributors and maintainers of this project, and in order to keep community open and welcoming, we ask to +As contributors and maintainers of this project, to keep community open and welcoming, we ask to
📜 Review details
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (9)
.github/FUNDING.yml.github/ISSUE_TEMPLATE/bug-report.yml.github/ISSUE_TEMPLATE/feature-request.yml.github/linters/actionlint.yml.github/workflows/linter.yml.gitignoreCODE_OF_CONDUCT.mdPULL_REQUEST_TEMPLATE.mdprofile/README.md
🧰 Additional context used
🪛 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)
⏰ 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 (10)
PULL_REQUEST_TEMPLATE.md (1)
1-8: LGTM! Clean and effective PR template.The template structure is clear and includes all essential fields for tracking changes. The format is standard for GitHub PR templates.
.github/FUNDING.yml (1)
1-2: LGTM! Valid funding configuration.The funding configuration correctly references the GitHub sponsor username.
.github/ISSUE_TEMPLATE/feature-request.yml (1)
1-11: LGTM! Well-structured feature request template.The template follows GitHub's issue form schema correctly with appropriate validation.
CODE_OF_CONDUCT.md (1)
1-102: LGTM! Standard and comprehensive code of conduct.This follows the Contributor Covenant v2.1 structure appropriately and covers all essential community guidelines.
.github/workflows/linter.yml (1)
1-17: External workflow reference is valid.The reusable workflow at
yii2-framework/actions/.github/workflows/super-linter.ymlexists, and thev1tag is available and properly configured in the external repository..github/ISSUE_TEMPLATE/bug-report.yml (2)
1-8: LGTM! Good security guidance.The security advisory warning is a best practice that appropriately directs users away from creating public security issues.
24-31: PHP version placeholder "8.5.0" is now valid.PHP 8.5 was released on November 20, 2025, and is the current latest stable release as of January 2026. The placeholder correctly references an existing PHP version and requires no changes.
Likely an incorrect or invalid review comment.
profile/README.md (2)
10-12: LGTM! Formatting updates are consistent.The changes from
-to+list markers are stylistic and don't affect the rendered content.
18-39: LGTM! Keyword formatting improved.The shift from bold to italic for keyword lines provides better visual distinction and is consistent across all package sections.
.gitignore (1)
7-8: Thecomposer.lockignore entry is appropriate for this repository.This is a community health repository with no PHP applications, no
composer.json, and no PHP scripts. The entry serves as a precautionary ignore rule (consistent with other conditional entries like.idea,.vagrant,nbproject, etc. marked as "if present"), which is appropriate for a template-style community health repository. No action needed.Likely an incorrect or invalid review comment.
1 participant
Summary by CodeRabbit
Chores
Documentation
✏️ Tip: You can customize this high-level summary in your review settings.