Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get "verified" badge for msys2/setup-msys2 on github marketplace #341

Open
dvrogozh opened this issue Dec 7, 2023 · 4 comments
Open

Get "verified" badge for msys2/setup-msys2 on github marketplace #341

dvrogozh opened this issue Dec 7, 2023 · 4 comments
Labels

Comments

@dvrogozh
Copy link

dvrogozh commented Dec 7, 2023

I stepped into the problem that I can't use msys2/setup-msys2 action within some (public open source) repositories. Specifically, it occurs that organizations, especially enterprise organization, might limit actions usage within organization. One of the limiter here is to allow actions "verified in the GitHub Marketplace". To me this occurred on intel/cloud-streaming#67. Failed workflow is not rendered on main PR page, need to look into actions tab (see https://github.com/intel/cloud-streaming/actions/runs/7123274817):

msys2/setup-msys2@v2 is not allowed to be used in intel/cloud-streaming. Actions in this workflow must be: within a repository owned by intel, created by GitHub, or verified in the GitHub Marketplace.

My usage for msys2/setup-msys2 action was to build ffmpeg which is a dependency for my project. I believe that's quite legitimate usage since that's the recommended way to build ffmpeg for Windows [1].

I think that getting "verified" badge, if possible, would be beneficial for both msys2 and greater community since it will allow to promote and scale msys2 usage for the wider audience. Can we try to obtain "verified" badge for msys2?

Unfortunately, I don't have any experience in the area of how to get such a badge. From a quick search, I see [2]. Quoting:

Actions with the , or verified creator badge, indicate that GitHub has verified the creator of the action as a partner organization. Partners can email [email protected] to request the verified creator badge.

I.e. as it seems this points to Github Partners program, whatever it is: https://partner.github.com/.

[1] https://ffmpeg.org/platform.html#Windows
[2] https://docs.github.com/en/actions/creating-actions/publishing-actions-in-github-marketplace#about-badges-in-github-marketplace

dvrogozh added a commit to dvrogozh/cloud-streaming that referenced this issue Dec 7, 2023
Within current github.com/intel org project this requires
additional setting for github project to allow msys2/setup-msys2
action since it does not have verified badge. Request for the
badge was sent to action owner, see [1].

See[1]: msys2/setup-msys2#341
Signed-off-by: Dmitry Rogozhkin <[email protected]>
dvrogozh added a commit to intel/cloud-streaming that referenced this issue Dec 7, 2023
Within current github.com/intel org project this requires
additional setting for github project to allow msys2/setup-msys2
action since it does not have verified badge. Request for the
badge was sent to action owner, see [1].

See[1]: msys2/setup-msys2#341
Signed-off-by: Dmitry Rogozhkin <[email protected]>
@lazka
Copy link
Member

lazka commented Dec 8, 2023

I've sent them an email, let's see.

@lazka
Copy link
Member

lazka commented Dec 9, 2023

They told me that the first requirement is to become a "Technology Partner" via https://partner.github.com/technology-partners, which is only possible for companies.

@lazka
Copy link
Member

lazka commented Dec 9, 2023

I'll leave this open as a reminder, but it's unlikely that we can do anything about this in the near future.

@lazka lazka added the blocked label Dec 9, 2023
@dvrogozh
Copy link
Author

They told me that the first requirement is to become a "Technology Partner" <...> which is only possible for companies.

Something I was afraid of. Thank you for update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants