Create SHA256SUM files
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Ideally:
* one for Go binaries, so that others can build binaries themself, verify hashes are identical, and sign the file,
* one for saved Docker containers, which cannot be independently verified, while it'll be nice to have a way to independently verify hash of downloaded file.
Probably useful: https://github.com/spencerdcarlson/sdc-tutorials/wiki/GnuPG-Signing-&-Checksums
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
The issue names no files, tests, or entry points. Start by examining how this repository builds Go binaries and publishes Docker containers, then identify where release artifacts are produced. Done means checksum files exist for the requested artifacts and their verification process is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops, release, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100