Archive in favor of official bazel-contrib/setup-bazel

[p0deje]

Hello, folks!

There is now a canonical GitHub Action to install and configure Bazel https://github.com/bazel-contrib/setup-bazel, hosted and maintained by Bazel Rules Authors SIG (https://bazel.build/community/sig).

Would you be open to archiving this action and suggesting to use a canonical one? This has already been done at https://github.com/bazelbuild/setup-bazelisk.

This way we could also use the Setup Bazel name on GitHub Marketplace.

[abhinavsingh]

Hi @p0deje , thanks for reaching out. Apologies for late reply, I am unable to catch up with GitHub open source efforts off late.

I have pinged stakeholders who are actively using setup-bazel in their public/private repositories. I am yet to hear back from them. IIUC, if I choose to archive this, it will break existing integrations and they may/may-not be ready for an immediate migration.

If it helps, I can surely add a cross-link, so that new users looking for Bazel workflows knows that there is a version maintained by SIG. Please let me know

[p0deje]

Apologies for late reply, I am unable to catch up with GitHub open source efforts off late.

No worries, thank you for taking the time and replying here.

IIUC, if I choose to archive this, it will break existing integrations and they may/may-not be ready for an immediate migration.

Not really, as long as repository exists - it will work. That's what https://github.com/bazelbuild/setup-bazelisk did - the repository is archived but users can still use until the migrate to a new action. It might help to add deprecation error using https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-a-warning-message and release a new version, but that's totally up to you.

If it helps, I can surely add a cross-link, so that new users looking for Bazel workflows knows that there is a version maintained by SIG. Please let me know

I believe something like bazelbuild/setup-bazelisk@fd3aad3 would be enough.