Skip to content

Conversation

@tonyandrewmeyer
Copy link
Collaborator

@tonyandrewmeyer tonyandrewmeyer commented Jun 25, 2025

It seems like the canonical organisation is now forcing all repositories to have a passing CLA check, so check if adding that workflow here solves that issue.

This is the workflow that the action recommends, with minor security improvements, and allowing workflow-dispatch.

Fixes #1851.

@james-garner-canonical
Copy link
Contributor

Looks good to me, and the cla-check passes. Resolves #1851

runs-on: ubuntu-latest
steps:
- name: Check if CLA signed
uses: canonical/has-signed-canonical-cla@5d1443b94417bd150ad234a82fe21f7340a25e4d # v2.1.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor:
I wonder if we could trust the canonical org and reference this action by branch like @v2

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd be on board with an entry for canonical to the .github/zizmor.yml policies being added in this PR.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wondered about that. You'd hope that we could. It feels pretty broad, but I guess it's sending the wrong message if we don't :)


on:
pull_request:
workflow_dispatch:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems a bit odd... what would be checked?

Perhaps authors of the last NN commits?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking it would be useful if it failed, then the contributor signed the CLA, and we could run it manually. But maybe we can just re-run the failed check, so that would be sufficient.

@tonyandrewmeyer
Copy link
Collaborator Author

It looks like maybe an org level one is meant to run. I've asked in MM for information. Maybe it's failing to run unless we duplicate it? That would be weird. I see that pattern in other repos, though.

@tonyandrewmeyer
Copy link
Collaborator Author

Apparently this is being run at an org level so no need to add it ourselves. I assume they will sort out the issue with it not running.

@tonyandrewmeyer tonyandrewmeyer deleted the add-cla-check branch June 25, 2025 02:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add the GitHub action to check contributors' CLA

3 participants