nextcloud / nextcloud/talk-desktop
Adding checksums to the releases
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 525
- Forks
- 85
- Avg merge
- 8h 5m
- Merged PRs (30d)
- 35
Description
Currently the releases are provided as archives without corresponding checksums.
It would be useful if some kind of checksum was provided. This would allow automated deployment scripts to check the downloaded file before use .
Contributor guide
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 file, test, or entry point is named. Start by tracing how this JavaScript/Electron project packages and publishes release archives, then determine where checksum artifacts should be generated and exposed; done means each release archive has a usable checksum for automated verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100