You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a requirement from my organisation that only allows GitHub Actions from verified creators in the marketplace.
Would that be an option for you to consider getting changesets as a verified creator there?
Being verified requires GitHub manually approving the verification request. I don't think they'd usually hand these out to OSS projects. If you check the verified creators on the marketplace, they're usually orgs from companies. I'd suggest requesting your org to relax the requirement.
There are a few OSS orgs/groups in there; and for some I don't see much difference with changesets. You might be right, they might be part of some large orgs/companies, but from what I see, some seem just like regular OSS groups.
Also to note that the verification process only need a couple of things, if we follow the docs on marketplace badges:
Verified ownership of their domain and has a verified badge on their profile (changesets.dev just needs to be verified by GitHub, which will give the org a verified tag)
Confirmed their email address so GitHub Support can reach the organization
I don't think any of these are requirements are limited to companies, but I'm no expert.
And I can't relax these requirements; that's unfortunately out of my hands here 🫤
Hello changesets maintainers;
I have a requirement from my organisation that only allows GitHub Actions from verified creators in the marketplace.
Would that be an option for you to consider getting
changesetsas a verified creator there?Thanks!