First, thank you for taking the time to contribute!
The following is a set of guidelines for contributors as well as information and instructions around our maintenance process. The two are closely tied together in terms of how we all work together and set expectations, so while you may not need to know everything in here to submit an issue or pull request, it's best to keep them in the same document.
Contributing isn't just writing code - it's anything that improves the project. All contributions for our GitHub Actions for WordPress are managed right here on GitHub. Here are some ways you can help:
If you're running into an issue with the action, please take a look through existing issues and open a new one if needed. If you're able, include a link to the log output from the failed run.
New features and enhancements are also managed via issues.
Pull requests represent a proposed solution to a specified problem. They should always reference an issue that describes the problem and contains discussion about the problem itself. Discussion on pull requests should be limited to the pull request itself, i.e. code review.
For more on how 10up writes and manages code, check out our 10up Engineering Best Practices.
This repository currently uses the develop branch to reflect active work and stable to represent the latest tagged release. Both should typically be usable and frequently the same, but we request that pull requests be opened against develop and usage of the action be against stable or a specific tag. New releases will be tagged as updates are made.
A new release pull requestwill be created automatically once a branch named release/X.Y.Z is pushed to GitHub.
The step by step release instructions can be found in .github/release-pull-request-template.md.