Skip to content

ci: allow DCO remediation commits - #138

Open
romeokienzler wants to merge 1 commit into
mainfrom
enable-dco-remediation
Open

romeokienzler wants to merge 1 commit into
mainfrom
enable-dco-remediation

Conversation

@romeokienzler

Copy link
Copy Markdown
Collaborator

Enables retroactive DCO sign-offs so the vendored history in #137 can be remediated.

Why

The DCO app reads allowRemediationCommits from .github/dco.yml on the default branch, and remediation is off by default. Without this file, remediation commits are parsed but silently discarded.

This is not theoretical — a correctly-formed third-party remediation commit was already pushed to #137 (8e1086c), and the DCO count stayed at 153 instead of dropping to 152. That commit only starts counting once this merges.

Why both flags

individual: true covers the 152 commits whose authors can sign off for themselves.

thirdParty: true is needed for one commit authored by whitesource-ets[bot], which cannot sign off for itself. Note that the app nests the third-party check inside the individual check (lib/dco.js), so thirdParty has no effect unless individual is also true.

Context

#137 vendors GeoDN-Discovery/overviews as a git subtree, bringing 153 upstream commits that predate this repo's DCO requirement. Rewriting that history to add sign-offs is not an option: it would flatten the subtree merge, and one person cannot sign off on another's commits. Remediation commits are the mechanism the DCO app provides for exactly this, and they leave history intact.

Merging this does not change any commit or sign-off state by itself — it only makes the remediation commits in #137 count.

🤖 Generated with Claude Code

The DCO app ignores remediation commits unless allowRemediationCommits is
set in .github/dco.yml on the default branch. Without this, retroactive
sign-offs are silently discarded -- the third-party remediation already
pushed to #137 left that PR's count unchanged at 153.

Enables both individual and third-party remediation. thirdParty is needed
because one of the vendored commits was authored by whitesource-ets[bot],
which cannot sign off for itself, and the app nests the third-party check
inside the individual one so both flags are required.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Signed-off-by: Romeo Kienzler <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant