-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarified DCO and CLA requirements #1354
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for making this happen! Unbelievable!!
Would love to understand if there are downsides to using the bot for the DCO.
Notes from today's CPC call: We assumed that @bensternthal would come back with an update to the PR accounting for the comments received. @bensternthal, please do let us know if you had something different in mind. |
Updated based on feebdack. Changes include: 1. Removing an auto generated TOC that was included by a visual studio plugin :| 2. Changed DCO instructions so that DCO bot is preferred but either method works.
@tobie Thanks for keeping me on my toes. Adjusted the PR with feedback. |
removed typo Signed-off-by: Benjamin Sternthal <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - Thanks for updating this!
Added a few suggestions.
Resolved Tobie's suggestions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Added clarifications for DCO & CLA, hoping to address #387, #632, and #778