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
bazel-contrib/setup-bazel is a great method to get bazel configured in the CICD environments.
However, when considered to be used in enterprise accounts workflows, the setup-bazel action is not available by default, because it is not verified in GitHub Marketplace.
Not only it is "not verified", but bazel-contrib/setup-bazel is not found the catalog.
The verification is simple email confirmation for the publisher to get a green tick. This will reduce the entry barrier in some use cases and thus increase the community.
Until then in such use case people would need to work around it: whitelist the action, which is some extra effort, and definitely a barrier for some use cases.
So I would really like to see setup-bazel published in github.com marketplace with a verified bazel-contrib account.
Let me know if I can help somehow.
Michael Pershyn
The text was updated successfully, but these errors were encountered:
I would like to publish an action to GitHub Marketplace, though the name is taken so I reached out to @abhinavsingh asking if he's open to archive his setup-bazel so we could publish this canonical action instead. I did it via Twitter but probably I just need to create an issue on GitHub.
If we cannot use the name, any suggestions for a different action name?
Dear Maintainers,
bazel-contrib/setup-bazel
is a great method to get bazel configured in the CICD environments.However, when considered to be used in enterprise accounts workflows, the
setup-bazel
action is not available by default, because it is not verified in GitHub Marketplace.Not only it is "not verified", but
bazel-contrib/setup-bazel
is not found the catalog.https://github.com/marketplace?category=&type=actions&verification=&copilot_app=&query=setup-bazel
The verification is simple email confirmation for the publisher to get a green tick. This will reduce the entry barrier in some use cases and thus increase the community.
Until then in such use case people would need to work around it: whitelist the action, which is some extra effort, and definitely a barrier for some use cases.
So I would really like to see
setup-bazel
published in github.com marketplace with a verifiedbazel-contrib
account.Let me know if I can help somehow.
Michael Pershyn
The text was updated successfully, but these errors were encountered: