Add community health files, issue templates, and CI workflows for better project management.

.github/FUNDING.yml

@@ -0,0 +1,2 @@
+---
+github: [terabytesoftw]

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -0,0 +1,31 @@
+---
+name: 🐛 Bug Report
+description: Let us know about problem
+body:
+  - type: markdown
+    attributes:
+      value: |
+        > ⚠️ DON'T CREATE SECURITY ISSUE here. For security vulnerabilities, please use the security advisory feature in the specific project repository instead.
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Provide a detailed description of the issue. Include all relevant information to help us understand and reproduce the problem.
+    validations:
+      required: true
+  - type: input
+    id: package-version
+    attributes:
+      label: Package version
+      description: Specify the exact package version you're using
+      placeholder: "0.1.0"
+    validations:
+      required: true
+  - type: input
+    id: php-version
+    attributes:
+      label: PHP version
+      description: Specify the exact PHP version you're using (run `php -v` to check)
+      placeholder: "8.5.0"
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -0,0 +1,11 @@
+---
+name: 🚀 Feature request
+description: Suggest an idea for improvement
+body:
+  - type: textarea
+    attributes:
+      label: Proposed new feature or change
+      description: |
+        Describe the feature and explain why it's needed.
+    validations:
+      required: true

.github/workflows/linter.yml

@@ -0,0 +1,17 @@
+---
+on:
+  - pull_request
+  - push
+
+name: linter
+
+permissions:
+  checks: write
+  contents: read
+  statuses: write
+
+jobs:
+  linter:
+    uses: yii2-framework/actions/.github/workflows/super-linter.yml@v1
+    secrets:
+      AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.gitignore

@@ -0,0 +1,51 @@
+# codecoverage (if present)
+code_coverage
+
+# codeception (if present)
+c3.php
+
+# composer
+composer.lock
+
+# gitHub copilot config (if present)
+.github/agents/**
+.github/copilot-instructions.md
+.github/copilot/**
+.github/instructions/**
+.github/prompts/**
+.github/skills/**
+
+# mac ds_store (if present)
+.DS_Store
+
+# netbeans project (if present)
+nbproject
+
+# node_modules (if present)
+node_modules
+package-lock.json
+
+# phpstorm project (if present)
+.idea
+
+# phpunit (if present)
+.phpunit.cache
+.phpunit.result.cache
+phpunit.xml*
+
+# vagrant (if present)
+.vagrant
+
+# vendor
+vendor
+
+# vscode project (if present)
+.vscode
+
+# windows thumbnail cache (if present)
+Thumbs.db
+
+# zend studio for eclipse project (if present)
+.buildpath
+.project
+.settings

CODE_OF_CONDUCT.md

@@ -0,0 +1,102 @@
+# Code of Conduct
+
+## Our Pledge
+
+As contributors and maintainers of this project, and in order to keep community open and welcoming, we ask to
+respect all community members.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Core team members are responsible for clarifying and enforcing our standards of acceptable behavior and will take
+appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Core team members have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits,
+issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for
+moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing
+the community in public spaces. Examples of representing a project or community include using an official email
+address, posting via an official social media account, within project GitHub, official forum or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting core team members. All
+complaints will be reviewed and investigated promptly and fairly.
+
+All core team members are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Core team members will follow these Community Impact Guidelines in determining the consequences for any action they
+deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in
+the community.
+
+**Consequence**: A private, written warning from core team members, providing clarity around the nature of the violation
+and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including
+unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding
+interactions in community spaces as well as external channels like social media. Violating these terms may lead to
+a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified
+period of time. No public or private interaction with the people involved, including unsolicited interaction with those
+enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate
+behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,8 @@
+# Pull Request
+
+| Q            | A                                                                  |
+| ------------ | ------------------------------------------------------------------ |
+| Is bugfix?   | ✔️/❌                                                              |
+| New feature? | ✔️/❌                                                              |
+| Breaks BC?   | ✔️/❌                                                              |
+| Fixed issues | <!-- comma-separated list of tickets # fixed by the PR, if any --> |

profile/README.md

@@ -1,25 +1,25 @@
 # PHP Forge: Code Craftsmanship for Reliability
 
-**PHP Forge** houses the foundational, framework-agnostic tools that power the next generation of PHP applications. 
+**PHP Forge** houses the foundational, framework-agnostic tools that power the next generation of PHP applications.
 
 ## 🔨 Our Philosophy
 
-* **Zero Dependencies:** Libraries that stand on their own.
-* **Battle Tested:** 100% Code Coverage.
-* **Strict Standards:** Strongly typed PHP and strict mode enabled.
+- **Zero Dependencies:** Libraries that stand on their own.
+- **Battle Tested:** 100% Code Coverage.
+- **Strict Standards:** Strongly typed PHP and strict mode enabled.
 
 ## 🛠️ The Toolset
 
-* **[Foxy](https://github.com/php-forge/foxy):** Fast, reliable, and secure BUN/NPM/Yarn/PNpM bridge for Composer.
+- **[Foxy](https://github.com/php-forge/foxy):** Fast, reliable, and secure BUN/NPM/Yarn/PNpM bridge for Composer.
 
 ## 🌐 Part of the Ecosystem
 
 Maintained by the core team of [yii2-framework](https://github.com/yii2-framework) and [yii2-extensions](https://github.com/yii2-extensions).
 
------
+---
 
 <div align="center">
-  <a href="https://github.com/sponsors/terabytesoftw"> 
+  <a href="https://github.com/sponsors/terabytesoftw">
     <img src="https://img.shields.io/badge/Sponsor-Click%20Here-pink?style=for-the-badge&logo=github-sponsors" alt="Sponsor php-forge on GitHub" height="40" />
   </a>
-</div>  
+</div>