Why isn't there an official GitHub Action for the Pact Verifier?
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 12
- Forks
- 10
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 8
Description
Hi,
I noticed that there's no official GitHub Action for running the pact_verifier_cli. Is there a specific reason for this? Are there any plans to provide one in the future?
Thanks!
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 existing GitHub Actions in the pactflow/actions repository and the referenced pact_verifier_cli entry point. The issue does not name a file, test, implementation scope, or acceptance criteria; done would require an agreed decision and defined requirements for an official verifier action.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- ci-cd, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100