Policy for running CI on releases
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 4.4k
- Forks
- 675
- Avg merge
- 22h 29m
- Merged PRs (30d)
- 1
Description
Define a policy for releasers running CI
- Cover test-node-candidate job
- Potentially to allow non-green runs where releaser is confident that the release isn't the cause.
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 the test-node-candidate job named in the issue and review the surrounding release process. The payload names no files or tests, so locate the relevant CI and release guidance before proceeding. Done means an agreed, documented policy covering this job and non-green runs when a releaser believes the release is not at fault.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, release
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100