I can't understand cla-bot warning

[knekrasov]

Can somebody please explain how can I get rid of this noisy message after each my push to GitHub?

Text:

Thanks for your contribution!
The CLA bot has flagged your contribution as not having a Contributor License Agreement
in place. Note that this is not needed in the overwhelming majority of instances and this warning will usually be ignored.
The code reviewers will make a determination and may ask you to sign a CLA or may choose to ignore this warning.
More information about this can be found here.

The proposed hyperlink leads to a short explanation what CLA means but doesn't explain what as a valid developer should I do next.
Just to clarify:

1. I keep committing from Citrix only, so my git uses only my seagate email address.
2. I use a dedicated GH account where Seagate email is set as primary.

Thanks in advance for any help.

cc @johnbent, @mukul-seagate11, @venkuppu-chn, @xahmad, @gauravchaudhari02

[mukul-seagate11]

@knekrasov,

cla-bot is a GitHub application for automation of Contributor License Agreements (CLAs). It checks whether contributors have signed an agreement and adding labels to PRs with sign-off signature. For that reason this bot automate the process of checking pull requests against a list of contributors or once approved by the owners

Moreover CLA documentation is in process which describe the process & workflow

[knekrasov]

@mukul-seagate11 That's understandable. But what I need to do to get rid of that message? :-) And moreover, if the developers have this kind of question unanswered, why do we actually need that cla-bot? It sounds like it doesn't help anybody.

[mukul-seagate11]

@knekrasov, We are in process of preparing documentation with instructors for developers & contributors, once ready we will share with you

[mukul-seagate11]

@mukul-seagate11 That's understandable. But what I need to do to get rid of that message? :-) And moreover, if the developers have this kind of question unanswered, why do we actually need that cla-bot? It sounds like it doesn't help anybody.

@johnbent, Would you like to comment on this please

[johnbent]

Thanks @knekrasov , these are good questions. To get rid of the warning the email that you use in your DCO signoff needs to be added to the .clabot file. @gauravchaudhari02 , is that correct? Since you have a @Seagate email address, we can do this. I hoped that we could add a wildcard for all @Seagate but I think we discovered that wasn't possible.

For external folks, they would have to initiate the legal process with us in the case where our gatekeepers deem it necessary. However, for the overwhelming majority of the cases, it shouldn't be necessary. @gauravchaudhari02 , can the gatekeeper clear the message or they just have to ignore it when they approve?

[johnbent]

@knekrasov I'm assuming this is resolved now and am closing this. Please reopen if you have further questions.

[knekrasov]

Sorry, @johnbent, but the problem is still there. I keep getting those noisy messages from cla-bot every time I push anything to github.

For instance, this one Seagate/cortx-hare#1259 (comment) is received 2 hours ago.