opf / opf/openproject-docker-compose
Sign all commits?
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 342
- Forks
- 315
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
to verify authenticity of commits it would be nice to always have signatures and not to only rely on access protections to the repository and having the possibility to check whether forks don't have any hidden modifications. Currently https://github.com/opf/openproject-docker-compose/commits/stable/17/ shows only around half the commits being signed.
https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule explains how branches could be configured to enforce signing commits.
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 by reviewing the stable/17 commit history and the linked GitHub documentation on branch protection and required signed commits. Confirm which repository branches are in scope and whether the required repository permissions are available. Done means the agreed branches enforce signed commits and the setting can be verified from GitHub.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100