VeryGoodOpenSource / VeryGoodOpenSource/very_good_workflows
docs: Package Update Policy - GitHub Actions
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 335
- Forks
- 89
- Avg merge
- 17h 19m
- Merged PRs (30d)
- 20
Description
Overview
This issue tracks the Package Update Policy for GitHub Actions across VeryGoodOpenSource repositories.
GitHub Actions update policy belongs with the workflows repo, where it has proper ownership and community visibility.
Scope
Define and document the policy for:
- How and when to update GitHub Actions versions (e.g.
actions/checkout,actions/setup-java, etc.) - Who is responsible for initiating updates
- Cadence for reviewing and bumping action versions
- How to handle breaking changes in upstream actions
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 by reviewing the workflows repository’s existing documentation and workflow definitions, including uses of actions/checkout and actions/setup-java. Document update timing, ownership, review cadence, and handling of upstream breaking changes; done means the policy is explicit and covers all listed areas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100