My organization has recently ran into a unique issue in one of our repositories. Beginning on November 28th, commits pushed by GitBook began requiring, and failing, DCO checks. Prior to the 28th only PRs were requiring DCO checks and commits were not, now commits are failing due to DCO checks. We are unable to identify a cause on our end, and the issue is exclusive to this repository and no settings were changed by us in this repo on or soon before the date the errors began. We reached out to GitBook directly, and they do not believe it is an issue with their bot their response below:
Thank you for your message.
The only check we do on our side is to make sure when the content is merged and live on your GitBook hosted page.
Those DCO checks seem to come from a requirement added by your team on that specific repo. As far as I can tell, all your commits - including the latest one - have been published and are live on your website, which means that GitBook is working as expected.
Please reach out to your team internally and check with them regarding those DCO checks and if they are necessary for that particular repo.
As I mentioned, though, this is not affecting GitBook in any way at this time from what I can see.
Hopefully that helps clarify.
Please don't hesitate to reach out if you have further questions.
I also opened a ticket directly with GitHub regarding the issue and they pointed me to this repo for assistance.
Is there any suggestions on settings that may be causing this issue or ways that we can resolve it while keeping the DCO checks enabled for PRs and the GitBook bot active for commits?
My organization has recently ran into a unique issue in one of our repositories. Beginning on November 28th, commits pushed by GitBook began requiring, and failing, DCO checks. Prior to the 28th only PRs were requiring DCO checks and commits were not, now commits are failing due to DCO checks. We are unable to identify a cause on our end, and the issue is exclusive to this repository and no settings were changed by us in this repo on or soon before the date the errors began. We reached out to GitBook directly, and they do not believe it is an issue with their bot their response below:
I also opened a ticket directly with GitHub regarding the issue and they pointed me to this repo for assistance.
Is there any suggestions on settings that may be causing this issue or ways that we can resolve it while keeping the DCO checks enabled for PRs and the GitBook bot active for commits?