pantheon-systems / pantheon-systems/plugin-release-actions
Update platform changelog with release details
Open
Nobody has claimed this yet.
build-tag-release
enhancement
- Dominant language
- Shell
- Stars
- 2
- Forks
- 1
- Avg merge
- 13h 6m
- Merged PRs (30d)
- 3
Description
On release, post a blog post with:
- link to repo
- link to releases
- link to wp.org/drupal.org
- the human friendly changelog from readme.md.
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 with readme.md to identify the human-friendly changelog and review how releases are handled in this repository. Clarify where the blog post should be published and which release entry point should trigger it. Done means the release post includes the repository, releases, wp.org/drupal.org, and readme.md changelog links.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- content, documentation, release
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100