fix(docs): Update workflows and documentation for improved CI/CD processes and feature clarity.

Author: terabytesoftw

.github/CODE_OF_CONDUCT.md

@@ -9,34 +9,34 @@ respect all community members.
 
 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
+- 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
+- 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 
+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 
+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 e-mail
+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.
 
@@ -54,7 +54,7 @@ deem in violation of this Code of Conduct:
 
 ### 1. Correction
 
-**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in 
+**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
@@ -66,7 +66,7 @@ and an explanation of why the behavior was inappropriate. A public apology may b
 
 **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 
+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

.github/FUNDING.yml

@@ -1,3 +1,2 @@
-# These are supported funding model platforms
-
+---
 github: [terabytesoftw]

.github/ISSUE_TEMPLATE.md

@@ -1,14 +1,15 @@
-### What steps will reproduce the problem?
+# Issue Report
 
-### What is the expected result?
+## What steps will reproduce the problem?
 
-### What do you get instead?
+## What is the expected result?
 
+## What do you get instead?
 
-### Additional info
+## Additional info
 
-| Q                | A
-| ---------------- | ---
-| Version          | 1.0.?
-| PHP version      | 
-| Operating system |
+| Q                | A     |
+| ---------------- | ----- |
+| Version          | 1.0.? |
+| PHP version      |       |
+| Operating system |       |

.github/PULL_REQUEST_TEMPLATE.md

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

.github/dependabot.yml

@@ -1,3 +1,4 @@
+---
 version: 2
 updates:
   # Maintain dependencies for GitHub Actions

.github/linters/actionlint.yml

@@ -0,0 +1,7 @@
+---
+paths:
+  .github/workflows/**/*.yml:
+    ignore:
+      - '"pull_request" section is alias node but mapping node is expected'
+      - '"push" section is alias node but mapping node is expected'
+      - "section is alias node but mapping node is expected"

.github/workflows/build.yml

@@ -1,33 +1,31 @@
+---
 on:
-  pull_request:
+  pull_request: &ignore-paths
     paths-ignore:
-      - 'docs/**'
-      - 'README.md'
-      - 'CHANGELOG.md'
-      - '.gitignore'
-      - '.gitattributes'
+      - ".gitattributes"
+      - ".gitignore"
+      - "CHANGELOG.md"
+      - "docs/**"
+      - "README.md"
 
-  push:
-    paths-ignore:
-      - 'docs/**'
-      - 'README.md'
-      - 'CHANGELOG.md'
-      - '.gitignore'
-      - '.gitattributes'
+  push: *ignore-paths
 
 name: build
 
+permissions:
+  contents: read
+  
 jobs:
   phpunit:
-    uses: php-forge/actions/.github/workflows/phpunit.yml@v1
+    uses: yii2-framework/actions/.github/workflows/phpunit.yml@v1
     secrets:
       CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
     with:
       composer-command: |
         composer require yiisoft/yii2:22.0.x-dev --prefer-dist --no-progress --no-interaction --no-scripts --ansi
       concurrency-group: phpunit-${{ github.workflow }}-${{ github.ref }}
   phpunit-compatibility:
-    uses: php-forge/actions/.github/workflows/phpunit.yml@v1
+    uses: yii2-framework/actions/.github/workflows/phpunit.yml@v1
     secrets:
       CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
     with:

.github/workflows/dependency-check.yml

@@ -1,22 +1,21 @@
+---
 on:
-  pull_request:
+  pull_request: &ignore-paths
     paths-ignore:
-      - 'docs/**'
-      - 'README.md'
-      - 'CHANGELOG.md'
-      - '.gitignore'
-      - '.gitattributes'
+      - ".gitattributes"
+      - ".gitignore"
+      - "CHANGELOG.md"
+      - "docs/**"
+      - "README.md"
 
-  push:
-    paths-ignore:
-      - 'docs/**'
-      - 'README.md'
-      - 'CHANGELOG.md'
-      - '.gitignore'
-      - '.gitattributes'
+  push: *ignore-paths
 
 name: Composer require checker
 
+permissions:
+  contents: read
+  pull-requests: write
+
 jobs:
   composer-require-checker:
-    uses: php-forge/actions/.github/workflows/composer-require-checker.yml@v1
+    uses: yii2-framework/actions/.github/workflows/composer-require-checker.yml@v1

.github/workflows/ecs.yml

@@ -1,22 +1,21 @@
+---
 on:
-  pull_request:
+  pull_request: &ignore-paths
     paths-ignore:
-      - 'docs/**'
-      - 'README.md'
-      - 'CHANGELOG.md'
-      - '.gitignore'
-      - '.gitattributes'
+      - ".gitattributes"
+      - ".gitignore"
+      - "CHANGELOG.md"
+      - "docs/**"
+      - "README.md"
 
-  push:
-    paths-ignore:
-      - 'docs/**'
-      - 'README.md'
-      - 'CHANGELOG.md'
-      - '.gitignore'
-      - '.gitattributes'
+  push: *ignore-paths
 
 name: ecs
 
+permissions:
+  contents: read
+  pull-requests: write
+
 jobs:
   easy-coding-standard:
-    uses: php-forge/actions/.github/workflows/ecs.yml@v1
+    uses: yii2-framework/actions/.github/workflows/ecs.yml@v1

.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 }}