chore: switch to has-signed-canonical-cla GH action #6109
Conversation
github-actions
bot
added
the
documentation
TheRealFalcon
force-pushed
the
cla
branch
2 times, most recently
from
82ab1bc to
7eb97a3
Compare
TheRealFalcon
changed the title
| If your company has signed the CLA for you, please contact us to help in | ||
| verifying which Launchpad/GitHub accounts are associated with the company. | ||
| `contributor license agreement <CLA_>`_ (CLA). A check is run against | ||
| every pull request to ensure that the CLA has been signed. |
There was a problem hiding this comment.
@TheRealFalcon Shall we make a note that August 2025 may require renewing your CLA signing?
There was a problem hiding this comment.
I don't think that makes sense in our first PR documentation as the people signing now won't need to re-sign. I think we'll just need to address it individually as it comes up on a PR.
There was a problem hiding this comment.
This looks good, it will affect some existing users who have relied upon our tools/.github-cla-signers file but haven't yet renewed their CLA specifically at https://ubuntu.com/legal/contributors/agreement.
One can confirm whether they need to sign the CLA with:
url https://cla.canonical.com/cla/check?github_usernames=YOUR_GITHUB_USERNAME
I just went through the process of signing the CLA again, which looks like the following as an individual contributor:
And choosing your associated email address from the github account:
Once that was done, I can confirm I've renewed my CLA:
$ curl https://cla.canonical.com/cla/check?github_usernames=blackboxsw
{"emails":{},"github_usernames":{"blackboxsw":true},"launchpad_usernames":{}}
We should rebase #6097 when this lands as I think @a-dubs is one of those users that isn't in the cla.canonical.com service.
2 participants
Proposed Commit Message
Additional Context
Test Steps
Merge type