dco

Recover unsigned commits by applying DCO sign-offs via amend, rebase, or cherry-pick.

3.4k|728|Updated Jun 28, 2022
One-click install
npx skills add https://github.com/linuxfoundation/crowd.dev --skill dco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dco
Source: https://github.com/linuxfoundation/crowd.dev/tree/main/.claude/skills/dco
Command: npx skills add https://github.com/linuxfoundation/crowd.dev --skill dco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DCO Sign-off Recovery helps engineers fix commits that are missing a Signed-off-by trailer by guiding retroactive sign-off and safe, repeatable workflows.

Core Features & Use Cases

  • Last-commit sign-off: Amend the most recent commit with --signoff and push with force-with-lease when needed.
  • Older-commit recovery: Interactively rebase from the parent of the unsigned commit to sign and reapply changes.
  • Cherry-pick or merge fixes: Reproduce unsigned commits via cherry-pick with sign-off to preserve history.
  • PR verification guidance: Validate that all commits on a branch carry DCO before submitting a PR.

Quick Start

Follow the guide to amend the last commit with a sign-off or recover older unsigned commits using interactive rebase or cherry-pick.

Frequently Asked Questions about dco

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a DCO sign-off to my last git commit?

To add a DCO sign-off to your last git commit, amend the commit using the --signoff flag and push with force-with-lease to safely update the remote branch.

How do I retroactively sign off older commits that are missing a DCO trailer?

Retroactively sign off older unsigned commits by running an interactive rebase from the parent of the unsigned commit to reapply changes with the sign-off trailer.

How do I fix unsigned commits introduced by a cherry-pick or merge across branches?

Fix unsigned cherry-pick or merge commits by reproducing the commits via cherry-pick with the --signoff flag to preserve branch history and pass DCO verification.

What is the safest way to force push git commits after applying a DCO sign-off?

The safest way to force push git commits after applying a retroactive DCO sign-off is using force-with-lease to prevent overwriting unexpected remote changes.

How do I validate that all commits on a branch carry a DCO sign-off before a PR?

Validate all commits on a branch carry a DCO sign-off before a PR by checking the commit history for the Signed-off-by trailer to ensure they pass PR verification.