AcademySoftwareFoundation / AcademySoftwareFoundation/MaterialX
Consider adopting signed release tags
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.3k
- Forks
- 464
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 11
Description
The OpenSSF Best Practices Badge suggests signing release tags. The process is simple, described here: simply create the release from a tag created with -s:
$ git tag -s v1.2.3
The project maintainer who creates the release tags needs a GPG key. Instructions for creating a key are described here.
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
Start with the OpenSSF Best Practices Badge criteria and GitHub's documentation on signing tags and generating a GPG key. Review how MaterialX release tags are currently created; done means the maintainer's release tags are signed and their signatures can be verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- release, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100