testcontainers / testcontainers/testcontainers-go
Bring back podman pipeline
Open
Nobody has claimed this yet.
dependencies
podman
- Dominant language
- Go
- Stars
- 5k
- Forks
- 637
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 26
Description
Proposal
In #625 we retired the podman pipeline, but we want to keep its value once the installation process gets fixed.
The pipeline is adding value in the sense of offering us a way to detect changes in Podman that could break testcontainers-go.
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
Review issue #625 and the repository's prior Podman pipeline to understand what was retired and how the installation process must be fixed. Restore the pipeline so it can detect Podman changes that could break testcontainers-go, and verify that the pipeline runs successfully after installation is corrected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100