Configure DCO signoff and GPG-signed commits in Git for LFX projects.
npx skills add https://github.com/linuxfoundation/lfx-skills --skill lfx-git-setup
Please help me install this Agent Skill. Skill: lfx-git-setup Source: https://github.com/linuxfoundation/lfx-skills/tree/main/lfx-git-setup Command: npx skills add https://github.com/linuxfoundation/lfx-skills --skill lfx-git-setup
This skill guides contributors through configuring DCO signoff and GPG-signed commits in Git for Linux Foundation projects, enabling compliant, verifiable contributions.
Begin by identifying your OS and follow the platform-specific steps in the references to enable DCO signoff and GPG-signed commits.
High-intent search queries and answers about installing and using this skill.
To configure GPG signing for Git commits on Linux Foundation projects, you need to generate a GPG key, configure Git to use it, and register the key on GitHub for verification. This skill provides step-by-step, platform-aware guidance for macOS, Linux, and Windows environments.
DCO signoff is a Developer Certificate of Origin process required for Linux Foundation project contributions to certify authorship. You need it when submitting pull requests to ensure your commits are compliant and verifiable.
Yes, you can set up Git commit signing on Windows using WSL2. This skill provides platform-specific guidance covering prerequisites, key generation, Git configuration, and GitHub key registration specifically for Windows users working within WSL2.
Your GPG-signed commit may not show as verified on GitHub if the GPG key is not properly registered to your GitHub account or if Git is not configured to use the correct key. This skill includes validation steps to ensure commits display proper verification signs.
Yes, generating a GPG key is part of the process to enable GPG-signed commits, which works alongside DCO signoff for Linux Foundation projects. The workflow covers key creation, Git configuration, and export to ensure compliant contributions.
The best way to validate your Git signing configuration is to follow the multi-phase workflow included in this skill, which covers verification, key creation, configuration, export, and validation steps to ensure your commits are properly signed and verified on GitHub.
MakisuoInstall and configure a local ClickHouse environment with clickhousectl.
prismaPrepare and submit external pull requests for the Prisma Next repository.
Community-AccessManage GitHub Discussions and audit community health files via the GitHub API.
Prorise-coolConfigure GPG commit signing for Git across Windows, macOS, and Linux.
