# Github API - GPG Signed Commit Support

**URL:** <https://community.n8n.io/t/github-api-gpg-signed-commit-support/16328>\
**Category:** Feature Requests\
**Created:** [August 4, 2022, 3:46am UTC](https://community.n8n.io/t/github-api-gpg-signed-commit-support/16328 "2022-08-04T03:46:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mskian](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/mskian/32/1914_2.png) [@mskian](https://community.n8n.io/u/mskian)\
**Post date:** [August 4, 2022, 3:46am UTC](https://community.n8n.io/t/github-api-gpg-signed-commit-support/16328/1 "2022-08-04T03:46:28Z")

</div>

Currently, **Github API** does not have the GPG Signed Commit option in **n8n**

> **[About commit signature verification - GitHub Docs](https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification)**
>
> Using GPG or S/MIME, you can sign tags and commits locally. These tags or commits are marked as verified on GitHub so other people can be confident that the changes come from a trusted source.

it will be more useful while doing automation tasks and commits

---

<div class="post-metadata">

**Author:** ![StefanR](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/stefanr/32/73825_2.png) [@StefanR](https://community.n8n.io/u/StefanR)\
**Post date:** [April 29, 2025, 9:09am UTC](https://community.n8n.io/t/github-api-gpg-signed-commit-support/16328/2 "2025-04-29T09:09:49Z")

</div>

Same problem.

Is anyone aware of a solution or workaround?