Skip to content

Commit 717ee9d

Browse files
PDowneyPDowney
authored
Workflows
1 parent e2f8fcd commit 717ee9d

File tree

6 files changed

+954
-2
lines changed

6 files changed

+954
-2
lines changed

‎.github/ISSUE_TEMPLATE/phpcs-failure.md‎

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
title: "PHPCS Code Standards Check Failed"
3+
labels: ["bug", "phpcs", "code-standards"]
4+
assignees: []
5+
---
6+
7+
## PHPCS Code Standards Check Failed
8+
9+
The PHPCS (PHP CodeSniffer) check has failed for the repository.
10+
11+
**Failure Details:**
12+
- **PHP Version:** {{ env.PHP_VERSION }}
13+
- **Workflow Run:** [View Details]({{ env.WORKFLOW_URL }})
14+
- **Run ID:** {{ env.RUN_ID }}
15+
16+
**What happened:**
17+
The code does not meet WordPress coding standards as defined by PHPCS.
18+
19+
**What needs to be done:**
20+
1. Review the PHPCS output in the failed workflow run
21+
2. Fix coding standard violations in the code
22+
3. Ensure all PHP files follow WordPress coding standards
23+
4. Test locally with: `phpcs --standard=WordPress --extensions=php .`
24+
25+
**Resources:**
26+
- [WordPress Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/php/)
27+
- [PHP CodeSniffer Documentation](https://github.com/squizlabs/PHP_CodeSniffer)
28+
29+
This issue was automatically created by the CI/CD pipeline.

‎.github/ISSUE_TEMPLATE/phpmd-failure.md‎

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
---
2+
title: "PHPMD Code Quality Check Failed"
3+
labels: ["bug", "phpmd", "code-quality"]
4+
assignees: []
5+
---
6+
7+
## PHPMD Code Quality Check Failed
8+
9+
The PHPMD (PHP Mess Detector) check has failed for the repository.
10+
11+
**Failure Details:**
12+
- **PHP Version:** {{ env.PHP_VERSION }}
13+
- **Workflow Run:** [View Details]({{ env.WORKFLOW_URL }})
14+
- **Run ID:** {{ env.RUN_ID }}
15+
16+
**What happened:**
17+
The code has quality issues detected by PHPMD analysis.
18+
19+
**What needs to be done:**
20+
1. Review the PHPMD output in the failed workflow run
21+
2. Address code quality issues such as:
22+
- Complex methods that should be simplified
23+
- Unused variables or parameters
24+
- Code duplication
25+
- Naming conventions
26+
- Design issues
27+
3. Test locally with: `phpmd . text cleancode,codesize,controversial,design,naming,unusedcode`
28+
29+
**Resources:**
30+
- [PHPMD Documentation](https://phpmd.org/)
31+
- [PHPMD Rules](https://phpmd.org/rules/index.html)
32+
33+
This issue was automatically created by the CI/CD pipeline.

‎.github/ISSUE_TEMPLATE/psalm-failure.md‎

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
---
2+
title: "Psalm Static Analysis Failed"
3+
labels: ["bug", "psalm", "static-analysis"]
4+
assignees: []
5+
---
6+
7+
## Psalm Static Analysis Failed
8+
9+
The Psalm static analysis check has failed for the repository.
10+
11+
**Failure Details:**
12+
- **PHP Version:** {{ env.PHP_VERSION }}
13+
- **Workflow Run:** [View Details]({{ env.WORKFLOW_URL }})
14+
- **Run ID:** {{ env.RUN_ID }}
15+
16+
**What happened:**
17+
Psalm has detected potential issues in the code through static analysis.
18+
19+
**What needs to be done:**
20+
1. Review the Psalm output in the failed workflow run
21+
2. Address static analysis issues such as:
22+
- Type errors
23+
- Undefined variables or methods
24+
- Incorrect return types
25+
- Unused code
26+
- Potential null pointer issues
27+
3. Test locally with: `./vendor/bin/psalm`
28+
29+
**Resources:**
30+
- [Psalm Documentation](https://psalm.dev/)
31+
- [Psalm Error Levels](https://psalm.dev/docs/running_psalm/error_levels/)
32+
33+
This issue was automatically created by the CI/CD pipeline.

‎.github/ISSUE_TEMPLATE/security-failure.md‎

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
title: "Security Vulnerability Detected"
3+
labels: ["security", "vulnerability", "critical"]
4+
assignees: []
5+
---
6+
7+
## Security Vulnerability Detected
8+
9+
A security vulnerability has been detected in the project dependencies.
10+
11+
**Failure Details:**
12+
- **PHP Version:** {{ env.PHP_VERSION }}
13+
- **Workflow Run:** [View Details]({{ env.WORKFLOW_URL }})
14+
- **Run ID:** {{ env.RUN_ID }}
15+
16+
**What happened:**
17+
The security checker has identified known vulnerabilities in one or more of the project's dependencies.
18+
19+
**What needs to be done:**
20+
1. Review the security check output in the failed workflow run
21+
2. Identify which dependencies have vulnerabilities
22+
3. Update vulnerable dependencies to secure versions
23+
4. If updates are not available, consider:
24+
- Finding alternative packages
25+
- Applying patches if available
26+
- Implementing workarounds
27+
5. Test the application after updates
28+
29+
**⚠️ Priority:** This is a security issue and should be addressed immediately.
30+
31+
**Resources:**
32+
- [Symfony Security Checker](https://github.com/FriendsOfPHP/security-advisories)
33+
- [WordPress Security Best Practices](https://developer.wordpress.org/plugins/security/)
34+
35+
This issue was automatically created by the CI/CD pipeline.

‎.github/ISSUE_TEMPLATE/wp-version-test-failure.md‎

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
title: "WordPress Version Compatibility Test Failed"
3+
labels: ["bug", "compatibility", "wordpress-version"]
4+
assignees: []
5+
---
6+
7+
## WordPress Version Compatibility Test Failed
8+
9+
The WordPress version compatibility test has failed.
10+
11+
**Failure Details:**
12+
- **PHP Version:** {{ env.PHP_VERSION }}
13+
- **WordPress Version:** {{ env.WP_VERSION }}
14+
- **Workflow Run:** [View Details]({{ env.WORKFLOW_URL }})
15+
- **Run ID:** {{ env.RUN_ID }}
16+
17+
**What happened:**
18+
The plugin failed to work correctly with WordPress {{ env.WP_VERSION }} on PHP {{ env.PHP_VERSION }}.
19+
20+
**What needs to be done:**
21+
1. Review the test output in the failed workflow run
22+
2. Identify compatibility issues with WordPress {{ env.WP_VERSION }}
23+
3. Fix any deprecated function calls or API usage
24+
4. Ensure plugin works correctly with this WordPress version
25+
5. Update plugin compatibility metadata if needed
26+
6. Test locally with WordPress {{ env.WP_VERSION }}
27+
28+
**Potential Issues:**
29+
- Deprecated WordPress functions
30+
- Changed WordPress APIs
31+
- PHP version incompatibilities with this WordPress version
32+
- Plugin initialization problems
33+
34+
**Resources:**
35+
- [WordPress Backward Compatibility](https://developer.wordpress.org/plugins/plugin-basics/determining-plugin-and-content-directories/)
36+
- [WordPress Deprecated Functions](https://developer.wordpress.org/reference/functions/)
37+
38+
This issue was automatically created by the CI/CD pipeline.

0 commit comments

Comments
 (0)