pact-foundation / pact-foundation/pact-cli
automated release triggers - cargo, docker, package managers
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 1
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 9
Description
Trigger the following on successful release
- switch to non-release/latest on tag release CI completion
- trigger docker build for tag and latest
- trigger cargo publish for tag
- trigger homebrew-tap
- trigger scoop
- trigger choco
apply 1-6 for pact-broker-client
add 4-6 to
Consider triggers from each of the individual cli's to do an update for the meta cli.
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 with successful release CI completion and the individual CLIs listed in the issue, then trace how the meta CLI is updated. Verify each requested tag/latest, Docker, Cargo, Homebrew, Scoop, and Chocolatey trigger across the named repositories; done means the specified release paths are automated and the meta CLI update path is defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, rust
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100