chainguard-dev / chainguard-dev/actions
Move TODO-s to issues
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 173
- Forks
- 83
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 11
Description
- boilerplate/action.yaml: # TODO(mattmoor): Cut a release of
boilerplate-checkwe can use instead. - setup-kind/action.yaml: required: true # TODO(mattmoor): Make this optional
- setup-melange/action.yaml: # TODO: the bubblewrap package available from "apt install"
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 reading boilerplate/action.yaml, setup-kind/action.yaml, and setup-melange/action.yaml and review the three listed TODOs. Create a separate issue for each TODO with its context, then remove the TODO entries so all three follow-ups are tracked in GitHub issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100