Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Plugin guidelines action #46

Closed
carstingaxion opened this issue May 29, 2024 · 0 comments · Fixed by #47
Closed

Add Plugin guidelines action #46

carstingaxion opened this issue May 29, 2024 · 0 comments · Fixed by #47

Comments

@carstingaxion
Copy link
Member

https://github.com/GatherPress/gatherpress/blob/main/.github/workflows/wordpress-org-plugin-guidelines.yml

carstingaxion added a commit that referenced this issue May 29, 2024
With the set goal in mind to become a versatile community plugin,
_label-printing_

> [...] should at **every time** align with the .org/plugin review
standards, at least with the automated part of the review process.
> 
> This is where the [Plugin Check
(PCP)](https://wordpress.org/plugins/plugin-check/) WordPress plugin
comes into play, because thankfully there is also a [corresponding
github action](https://github.com/swissspidy/wp-plugin-check-action).
> ### Description of the Change
> 
> [...] we should introduce this action into our default `push` and
`pull_request` workflows. This would also be a nice aspect to promote
further, saying "We align with the guidelines not only once (like
normal), but with every release".
> 
> ~Closes #~

Closes #46 

> ### How to test the Change
> 
> I hope to see the test running within this PR, to get a basic testing.
> ### Changelog Entry
> 
> > Added - Test against standards for the WordPress.org plugin
directory

---

Cloned PR from GatherPress/gatherpress#616

---

### Code Checklist
- [x] tested
- [ ] documented
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant