pantheon-systems / pantheon-systems/plugin-release-actions
Automate readme.txt changelog
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 2
- Forks
- 1
- Avg merge
- 13h 6m
- Merged PRs (30d)
- 3
Description
Instead of feature branch/dev branch requiring an update to both readmes, engineers only update readme.md.
As part of the release PR, the changelog content is copied from readme.md (or a dedicated changelog.md) to readme.txt.
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 tracing the release PR workflow and how it handles readme.md, readme.txt, and any dedicated changelog.md. Define the release behavior so engineers update only readme.md, then verify that the changelog content is copied into readme.txt during the release PR.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100