WordPress / WordPress/wpdev-docker-images
Update GitHub Action workflow files to make use of the reusable pattern
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 69
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
When Dependabot opens a pull request to update third-party action versions, the PR will always need manual intervention because the template file is not updated and the next run of update.php erases the changes to the .github/workflows directory.
Dependabot does support specifying multiple directories, but it's unclear whether
- a file with invalid YAML (which the template is considered) would be updated correctly.
- a file outside of the
.githubfolder would be updated
If the file must be valid YAML, then the tokens could be changed to be within comments. If the file needs to be inside .github/, perhaps the template could be moved.
Contributor guide
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 reading update.php and the template file that generates the .github/workflows directory. Check how Dependabot handles the template's YAML and location, including its support for multiple directories. Done means Dependabot updates third-party action versions without manual intervention and a later update.php run no longer erases those changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, php
- Domain
- ci-cd, devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100