The Developer Certificate of Origin appears to be widely used in open source at this point, including support at GitHub and use by GitLab community edition.

In accepting a pull request, many folks (including me) like to use a "squash" merge where all commits are concatenated into a single commit. But then, this isn't exactly what the contributor signed, and the person merging the pull request gets write access to the combined commit message.

So does the DCO make it impossible to do squash-and-merge?

  • 1
    So this Developer Certificate of Origin thing is just a text document? No digital signatures or anything like that? How could it possibly make a technical maneuver like a "squash and merge" impossible? – Robert Harvey Jun 15 '18 at 17:16
  • Is the result of the squash merge the same? In other words, is the contribution in whole applied as provided? If so, I believe that would fall within the spirit of the Development Certificate of Origin's purpose. – Berin Loritsch Jun 15 '18 at 17:17
  • @RobertHarvey if you type your name into a web form, it's a valid signature (but IANAL!). If I change the submission data, did you still sign the result? – Dav Clark Jun 15 '18 at 17:48
  • So to be clear, I mean legally possible. Or perhaps just "legal." – Dav Clark Jun 15 '18 at 17:48
  • 1
    For that, you need to talk to our legal department. – Robert Harvey Jun 15 '18 at 23:24

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.