chainguard-dev / chainguard-dev/actions
@vaikas @cpanato maybe we should beef up the `setup-kind` testing here to setup `sigstore/scaffolding`? Then we should be able to detect this pretty quickly 🤞
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 173
- Forks
- 83
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 11
Description
@vaikas @cpanato maybe we should beef up the `setup-kind` testing here to setup `sigstore/scaffolding`? Then we should be able to detect this pretty quickly 🤞
Originally posted by @mattmoor in https://github.com/chainguard-dev/actions/pull/173#discussion_r1022079625
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 with the setup-kind testing referenced in the issue and review pull request #173, especially the linked discussion. Determine how to provision sigstore/scaffolding in that test setup; done means the expanded test detects the reported problem reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100