WordPress / WordPress/php-toolkit
Set up a CI pipeline with GitHub's actions
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 61
- Forks
- 21
- Avg merge
- 19h 34m
- Merged PRs (30d)
- 7
Description
Automate the CI process with GitHub actions:
- step running unit tests for PHP == 7.4,
(as an intermediate step #25) - step running unit tests for PHP == 7.0,
(finally done with #86) - step with matrix unit tests for all versions > 7.0,
- step with matrix unit tests for all versions > 7.4,
(as an intermediate step #25) - step for automatic linting, after #26
- step for coding standards check, after #26
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's GitHub Actions setup and the work tracked in issue #26. Add the remaining automatic linting and coding-standards checks after that dependency is complete, and verify that the workflow runs them alongside the existing PHP unit-test matrix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, php
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100