hashicorp / hashicorp/actions-pr-guidelines
Release bits?
Open
- Dominant language
- No language data
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Do we need to set up a way to automate releases? Say, I push up a change, open a PR, get it reviewed, merge into main, a release gets automatically sent out and the tag is updated (i.e. v1 always points to the newest tag)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the repository's existing workflow configuration and the proposed merge-to-main release flow. Define how an automatic release should be triggered and how the v1 tag should track the newest release tag; done means the process is specified and verified end to end.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100