Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
It removes the GH workflow for podman, as it started to fail yesterday, pressumably caused by how podamn is installed in the GH runner.
We verified that the last time the podman pipeline passed, it was 4 days ago, using the very same runner than when it started to fail yesterday:
馃煝 last green build: https://github.com/testcontainers/testcontainers-go/actions/runs/3451793607/jobs/5761263469
馃敶 first broken build: https://github.com/testcontainers/testcontainers-go/actions/runs/3469834261/jobs/5797300820
Why is it important?
The GH check for podman is not required by the branch protection, but it's causing noise in the PRs and merge commits.
Follow-ups
Bring back the pipeline once the installation of podman in the ubuntu runner is fixed, probably at the package manager level.
See #626