sanitizers / sanitizers/patchback-github-app
[research] Producing GPG-signed commits
Open
enhancement
help wanted
- Dominant language
- Python
- Stars
- 14
- Forks
- 10
- Avg merge
- 4m
- Merged PRs (30d)
- 3
Description
This is not of an immediate urgency but it'd be cool for the cherry-picked commits to be PGP-signed and show up as Verified on GitHub.
There's two known problems with this at the moment, though:
- GitHub docs don't document the signing considerations for GitHub Apps clearly enough: https://github.community/t/how-to-properly-gpg-sign-github-app-bot-created-commits/131364?u=webknjaz
- pygit2 that we rely on currently does not expose any APIs for applying signatures to commits. It'd require some effort to get them exposed from libgit2 library that it wraps: https://github.com/libgit2/pygit2/issues/647#issuecomment-689527336
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 linked pull request #53, then read the GitHub Apps signing discussion and the referenced pygit2/libgit2 issue. Determine whether the project can support signed cherry-picked commits with the available APIs; done means the approach is agreed and commits appear as Verified on GitHub.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, python
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100