Skip to content

Commit 3e72e7a

Browse files
PDowneyPDowney
authored
First Commit
1 parent 497555f commit 3e72e7a

28 files changed

+2013
-0
lines changed

‎.github/CODE_OF_CONDUCT.md‎

Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
We as members, contributors, and leaders pledge to make participation in our
6+
community a harassment-free experience for everyone, regardless of age, body
7+
size, visible or invisible disability, ethnicity, sex characteristics, gender
8+
identity and expression, level of experience, education, socio-economic status,
9+
nationality, personal appearance, race, religion, or sexual identity and orientation.
10+
11+
We pledge to act and interact in ways that contribute to an open, welcoming,
12+
diverse, inclusive, and healthy community.
13+
14+
## Our Standards
15+
16+
Examples of behavior that contributes to a positive environment for our community include:
17+
18+
* Demonstrating empathy and kindness toward other people
19+
* Being respectful of differing opinions, viewpoints, and experiences
20+
* Giving and gracefully accepting constructive feedback
21+
* Accepting responsibility and apologizing to those affected by our mistakes
22+
* Focusing on what is best for the overall community
23+
24+
Examples of unacceptable behavior include:
25+
26+
* The use of sexualized language or imagery, and sexual attention or advances
27+
* Trolling, insulting or derogatory comments, and personal or political attacks
28+
* Public or private harassment
29+
* Publishing others' private information without explicit permission
30+
* Other conduct which could reasonably be considered inappropriate in a professional setting
31+
32+
## Enforcement Responsibilities
33+
34+
Project maintainers are responsible for clarifying and enforcing our standards of
35+
acceptable behavior and will take appropriate and fair corrective action in
36+
response to any behavior that they deem inappropriate, threatening, offensive,
37+
or harmful.
38+
39+
## Scope
40+
41+
This Code of Conduct applies within all community spaces, and also applies when
42+
an individual is officially representing the community in public spaces.
43+
44+
## Enforcement
45+
46+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
47+
reported to the project maintainers responsible for enforcement at
48+
peter@visistruct.com.
49+
50+
Project maintainers will review and investigate all complaints, and will
51+
respond in a way that they deem appropriate to the circumstances.
52+
53+
## Attribution
54+
55+
This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org),
56+
version 2.1, available at
57+
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html).

‎.github/FUNDING.yml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
# These are supported funding model platforms
2+
3+
#patreon: # Replace with a single Patreon username
4+
5+
github: enginescript
6+
ko_fi: enginescript
7+
buy_me_a_coffee: enginescript
8+
liberapay: enginescript
9+
thanks_dev: gh/pdowney

‎.github/ISSUE_TEMPLATE/compatibility-test-failure.md‎

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
name: "PHP Compatibility Test Failure"
3+
about: "Automated issue created when PHP compatibility tests fail"
4+
title: PHP {{ env.PHP_VERSION }} Compatibility Test Failure
5+
labels: bug, compatibility, automated
6+
assignees: []
7+
---
8+
9+
## PHP Compatibility Test Failure
10+
11+
The automated compatibility test for PHP {{ env.PHP_VERSION }} has failed.
12+
13+
### Details
14+
15+
- **PHP Version:** {{ env.PHP_VERSION }}
16+
- **WordPress Version:** Latest
17+
- **Test Date:** {{ date | date('YYYY-MM-DD HH:mm:ss') }}
18+
- **Workflow Run:** [View detailed logs]({{ env.WORKFLOW_URL }})
19+
20+
### Next Steps
21+
22+
This issue has been automatically created because the Simple WP Optimizer plugin failed to load properly with PHP {{ env.PHP_VERSION }}. This could indicate compatibility issues that need to be addressed.
23+
24+
#### Recommended Actions:
25+
26+
1. Review the workflow logs for specific error messages
27+
2. Check for PHP {{ env.PHP_VERSION }} specific syntax or function compatibility issues
28+
3. Test locally with PHP {{ env.PHP_VERSION }} to reproduce the issue
29+
4. Make necessary code updates to ensure compatibility
30+
31+
Once fixed, please close this issue and reference it in the changelog.
32+
33+
---
34+
35+
*This issue was automatically generated by the PHP Compatibility WordPress Test workflow.*

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

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

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

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

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

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
---
2+
name: "PHPStan Analysis Failure"
3+
about: "Automated issue created when PHPStan static analysis fails"
4+
title: "PHPStan for WordPress Analysis Failed - PHP {{ env.PHP_VERSION }}"
5+
labels: ["bug", "phpstan", "static-analysis", "wordpress"]
6+
assignees: []
7+
---
8+
9+
## PHPStan for WordPress Static Analysis Failure
10+
11+
**PHP Version:** {{ env.PHP_VERSION }}
12+
**Workflow Run:** [{{ env.RUN_ID }}]({{ env.WORKFLOW_URL }})
13+
**Date:** {{ date | date('YYYY-MM-DD') }}
14+
15+
### Description
16+
The PHPStan for WordPress static analysis check has failed during the automated testing process.
17+
18+
### What happened?
19+
PHPStan for WordPress detected potential code issues during static analysis. This could indicate:
20+
21+
- Type safety issues specific to WordPress APIs
22+
- Potential bugs or inconsistencies in WordPress plugin code
23+
- WordPress coding standard violations
24+
- Incorrect usage of WordPress functions or hooks
25+
26+
### Next Steps
27+
1. Review the workflow logs at the link above
28+
2. Check the specific PHPStan error messages
29+
3. Fix any identified code issues
30+
4. Ensure WordPress-specific type annotations are correct
31+
5. Re-run the workflow to verify fixes
32+
33+
### Additional Information
34+
- This check uses WordPress-specific PHPStan rules
35+
- The analysis helps catch WordPress-related coding issues early
36+
- Consider updating code to follow WordPress best practices
37+
38+
---
39+
*This issue was automatically created by the PHPStan for WordPress workflow failure.*

‎.github/ISSUE_TEMPLATE/plugin-check-failure.md‎

Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
---
2+
name: "WordPress Plugin Check Failure"
3+
about: "Automated issue created when WordPress Plugin Check fails"
4+
title: WordPress Plugin Check Failure
5+
labels: bug, plugin-check, automated
6+
assignees: []
7+
---
8+
9+
## WordPress Plugin Check Failure
10+
11+
The WordPress Plugin Check action has identified issues with the Simple WP Optimizer plugin.
12+
13+
### Details
14+
15+
- **Test Date:** {{ date | date('YYYY-MM-DD HH:mm:ss') }}
16+
- **Workflow Run:** [View detailed logs]({{ env.WORKFLOW_URL }})
17+
18+
### Next Steps
19+
20+
This issue has been automatically created because the WordPress Plugin Check found issues with the plugin that should be addressed. The check performed the following specific tests:
21+
22+
#### Categories:
23+
- **Accessibility**: Checks for accessibility compliance issues
24+
- **General**: General WordPress coding standards and best practices
25+
- **Performance**: Tests that identify performance bottlenecks
26+
- **Plugin Repo**: Requirements for WordPress.org plugin repository
27+
- **Security**: Security-focused checks to identify vulnerabilities
28+
29+
#### Specific Checks:
30+
- **i18n_usage**: Proper internationalization usage
31+
- **code_obfuscation**: Detecting potentially obfuscated code
32+
- **direct_db_queries**: Identifying direct database queries that bypass WordPress APIs
33+
- **enqueued_scripts_in_footer**: Ensuring scripts are properly enqueued in the footer
34+
- **enqueued_scripts_size**: Checking for excessively large script files
35+
- **enqueued_styles_scope**: Ensuring styles are properly scoped
36+
- **file_type**: Checking for proper file types and formats
37+
- **late_escaping**: Ensuring output is properly escaped
38+
- **localhost**: Checking for references to localhost or development environments
39+
- **no_unfiltered_uploads**: Ensuring uploads are properly filtered
40+
- **performant_wp_query_params**: Checking for inefficient WP_Query parameters
41+
- **plugin_header_text_domain**: Verifying correct text domain in plugin header
42+
- **plugin_readme**: Checking the plugin readme file format
43+
- **plugin_review_phpcs**: PHP CodeSniffer checks for WordPress standards
44+
- **plugin_updater**: Checking plugin update mechanisms
45+
- **trademarks**: Checking for potential trademark violations
46+
47+
#### Recommended Actions:
48+
49+
1. Review the workflow logs for specific error messages and warnings
50+
2. Address each identified issue in the plugin code
51+
3. Test locally using the [WordPress Plugin Check tool](https://github.com/WordPress/plugin-check) to verify fixes
52+
4. Submit a pull request with the necessary changes
53+
54+
Once all issues are fixed, please close this issue and reference it in the changelog.
55+
56+
### About WordPress Plugin Check
57+
58+
The WordPress Plugin Check tool helps plugin authors create plugins that follow WordPress best practices. It checks for issues related to security, performance, and compatibility to ensure plugins work well in the WordPress ecosystem.
59+
60+
---

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

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

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

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

‎.github/ISSUE_TEMPLATE/wp-dependencies-failure.md‎

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
---
2+
name: "WordPress Dependencies Monitoring Failure"
3+
about: "Automated issue created when WordPress dependencies monitoring fails"
4+
title: "WordPress Dependencies Monitoring Failed - PHP {{ env.PHP_VERSION }}"
5+
labels: ["bug", "dependencies", "wordpress", "monitoring"]
6+
assignees: []
7+
---
8+
9+
## WordPress Dependencies Monitoring Failure
10+
11+
**PHP Version:** {{ env.PHP_VERSION }}
12+
**Workflow Run:** [{{ env.RUN_ID }}]({{ env.WORKFLOW_URL }})
13+
**Date:** {{ date | date('YYYY-MM-DD') }}
14+
15+
### Description
16+
The WordPress dependencies monitoring check has failed during the automated testing process.
17+
18+
### What happened?
19+
The WordPress dependencies monitoring action detected issues with dependencies. This could indicate:
20+
21+
- Outdated WordPress core dependencies
22+
- Incompatible plugin dependencies
23+
- Missing or deprecated WordPress functions being used
24+
- WordPress version compatibility issues
25+
- Plugin dependency conflicts
26+
27+
### Potential Issues
28+
- **WordPress Core Updates:** WordPress core may have been updated with breaking changes
29+
- **Plugin Dependencies:** Dependencies used by the plugin may be outdated or incompatible
30+
- **API Changes:** WordPress APIs used by the plugin may have changed
31+
- **Deprecated Functions:** The plugin may be using deprecated WordPress functions
32+
33+
### Next Steps
34+
1. Review the workflow logs at the link above
35+
2. Check for specific dependency warnings or errors
36+
3. Update WordPress core compatibility if needed
37+
4. Review plugin dependencies for compatibility
38+
5. Update any deprecated WordPress function calls
39+
6. Test with the latest WordPress version
40+
7. Re-run the workflow to verify fixes
41+
42+
### Additional Information
43+
- This monitoring helps ensure WordPress ecosystem compatibility
44+
- Regular dependency monitoring prevents future compatibility issues
45+
- Consider updating minimum WordPress version requirements if needed
46+
47+
---
48+
*This issue was automatically created by the WordPress Dependencies Monitoring workflow failure.*

0 commit comments

Comments
 (0)