pantheon-systems / pantheon-systems/plugin-release-actions
Use autotag as part of "prepare release PR" rather than determining major/minor/patch as part of feature dev.
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 2
- Forks
- 1
- Avg merge
- 13h 6m
- Merged PRs (30d)
- 3
Description
- opt-in to using autotag as part of the prepare release PR
- plugin README should include autotag documentation
- plugin PR template should reference autotag tags.
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 locating the prepare release PR workflow, the plugin README, and the plugin PR template. Read how release tags are currently determined and how the workflow opts into actions. Done means autotag can be opted into during release preparation, with its tags documented in the README and referenced by the PR template.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- ci-cd, documentation, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100