Have Gitpod-based commits GPG-signed
Open
Nobody has claimed this yet.
meta: never-stale
team: webapp
type: feature request
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
There are some projects that requires commits to be GPG-signed to verify the authenticity of a contributor. Gitpod should be able make commits GPG-signed as a preference or automatically like browser-editing.
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
The issue names no files, tests, or entry points. Start by tracing how Gitpod handles commits and compare that with the existing browser-editing behavior mentioned in the issue. Done should include an agreed preference or automatic signing flow for Gitpod-based commits, with its verification behavior documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- developer-experience, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100