Actions are just GitHub repositories, therefore any redirects in place on GitHub will carry through to usages of GitHub Actions. GitHub automatically creates a redirect when a repository is transferred, so the GitHub Actions will continue to work as-is. The GitHub Marketplace for Actions is effectively just a helpful representation of the
action.yml for each submitted Action: submitting an Action to the marketplace doesn’t influence the Action itself – whether it’s listed in the Marketplace or not, it’ll keep working as-is, because
ansible/ansible-lint-action will resolve to the Action’s repository.
verified badge in the Marketplace: there’s some nuance here because the
verified badge that appears on an organisation’s GitHub page (e.g: github.com/ansible) is not the same verified badge you see in the Marketplace. The Marketplace
verified badge refers to Publisher Verification status, which must be approved by GitHub. Historically it was granted by GitHub to commercial partners but it’s now available for any organisation to apply for, as described in Applying for publisher verification for your organization.
You can confirm if the Ansible Community organisation has passed Publisher Verification by visiting the following page: https://github.com/organizations/ansible-community/settings/publisher
So to recap:
You can transfer a GitHub Action from one organisation (or user) to another, because github.com’s repository redirects also impact Actions: no change is needed from users, the Action will continue to work as-is.
verified status seen on a GitHub organisation’s profile is not the same as Marketplace verification. Marketplace verification is specific to a GitHub organisation and must be granted by GitHub, it is unlikely that
ansible-community already has verified status and so the verified badge will be lost on the GitHub Action’s marketplace page.