don't rebuild full docker/binary matrix every pull request
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11.3k
- Forks
- 488
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 11
Description
we're building like 30? docker images on every single pull request push - should we perhaps only run one of php 8.2/8.3/8.4/8.5 each on normal pushes and manually tag "ready to test" for the full matrix before merge?
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 tracing the pull request build configuration that creates the Docker and binary matrix across PHP 8.2–8.5. Define how normal pushes select one version per line and how a "ready to test" tag triggers the full matrix; done means both paths are available and the normal pull request build no longer runs every image.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, php
- Domain
- build-system, ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100