semantic-release / semantic-release/github
Include checksums in release notes
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 534
- Forks
- 150
- Avg merge
- 1m
- Merged PRs (30d)
- 3
Description
It's a very good practice to do that but sadly GitHub Releases lack this feature out-of-the-box.
We could have an option for this plugin to calculate the checksum for each file it's going to upload and populate a table (or something like that) in the GitHub release notes with this information.
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
No files or tests are named. Start by tracing the plugin's GitHub release upload and release-notes handling, then identify where uploaded files and release-body content are assembled. Done means an option calculates checksums for each uploaded file and includes them in the generated release notes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100