Skip to content
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.

Coding standards audit #24

Closed
jeffpaul opened this issue Mar 25, 2020 · 1 comment
Closed

Coding standards audit #24

jeffpaul opened this issue Mar 25, 2020 · 1 comment
Labels
task A task to be done, as opposed to a bug report/feature request

Comments

@jeffpaul
Copy link
Member

Migrated from: audrasjb/wp-autoupdates#75
Previously opened by: @jeffpaul
Original description:

While a WPCS audit will be ideal (required?) before submitting for a WordPress core feature plugin merge proposal, we may be even better served to have a pre-commit hook that runs WPCS against our commits. Similarly having WPCS as a PR check via something like GitHub Actions or Travis or whatever is also very worthwhile. Someone want to work on adding that to this repo?

@jeffpaul jeffpaul added the task A task to be done, as opposed to a bug report/feature request label Mar 25, 2020
@jeffpaul jeffpaul added this to the Future Release milestone Mar 25, 2020
@pbiron
Copy link
Contributor

pbiron commented May 17, 2020

While not done via GitHub actions, this has been addressed, most importantly in #119 and #124, so I'm closing this.

@pbiron pbiron closed this as completed May 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
task A task to be done, as opposed to a bug report/feature request
Projects
None yet
Development

No branches or pull requests

2 participants