Closed DL6ER closed 5 years ago
I'm not opposed to this at all; however, I think some orgs that are stricter in their requiring of DCO might not love this idea, so what about adding this feature as an additional field in the .github/dco.yml
as allowPRSignOff: true
(and have it be false by default)?
Yes, that would be a great idea.
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
I think this would help a lot with usability.
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
Yes, this is still relevant.
Is anyone working on this?
Hi, I suggest an alternative solution in https://github.com/probot/dco/issues/105. Feel free to share your thoughts.
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
Dear DCO developers,
we use your bot to enforce Sign-Off lines by our users in our project. However, we often receive external contributions from users with few (or no) previous experience with Github and adding a Signed-Off-by message in all of their commits (by walking the tree and rewriting things) is something that is a bit complex to explain to newcomers.
Hence, our own solution was to ask users to just edit in the requested line into the pull request message and we accept this as being equivalent. However, DCO does not read the pull request text for these lines and hence we have to ignore its false positive for merging.
Can interpreting the pull request text be added in order to ease the process for
git
newcomers?