hashicorp / hashicorp/actions-pr-guidelines
Do we need tests?
Open
- Dominant language
- No language data
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
If we were to automate releasing upon merge to main, should we at least have some safeguards put in i.e. tests in order to ensure we're not pushing something disastrous into main?
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by reviewing the PR Guidelines workflow and the proposed release-on-merge path; determine which safeguards are required before releases are automated to main. Done means the need for safeguards is decided and the applicable tests or checks are identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100