Transfer bazel-watcher to bazel-contrib

[meteorcloudy]

Description:

This issue proposes transferring the bazel-watcher repository from the bazelbuild GitHub organization to the bazel-contrib GitHub organization, which is owned by the Community for Bazel project under the Linux Foundation.

GitHub Discussion: https://github.com/orgs/bazelbuild/discussions/2

Impacts:

• GitHub issues & PRs will be transferred to the new repository.
• Branch protection rules will need to be transferred to the new repository.
• Individual maintainers will be transferred to the new repository.
• GitHub teams will NOT be transferred to the new repository and will need to be re-created.
• Bazel CI configurations will need to be updated to point to the new repository.

Read more on Transferring a repository from GitHub documentation.

Checklist:

• [ ] Obtain approval from the current project maintainers (@achew22 ).
• [ ] Obtain approval from the bazel-contrib SIG (@alexeagle).
• [ ] Initiate the transfer process on GitHub (@meteorcloudy).
• [ ] Update Bazel CI settings and confirm presubmit & postsubmit work (@meteorcloudy).

[alexeagle]

Notes from SIG meeting:

https://bazel-contrib.github.io/SIG-rules-authors/hosting-policy.html#adding-criteria Criteria 9 is that this should work with bzlmod, https://github.com/bazelbuild/bazel-watcher/pull/647 seems like maybe it still requires a WORKSPACE file.

Consensus: let's not include this in today's bulk-transfer. Can be re-visited in a later SIG meeting.

[meteorcloudy]

@josephperrott @achew22 Can you please approve this transfer?

[github-actions[bot]]

Stale issue message

[meteorcloudy]

not stale

[github-actions[bot]]

Stale issue message

[meteorcloudy]

Looks like this project is abandoned? Maybe we should just archive it.

[achew22]

The project is not abandoned. The requirement that I have before accepting a pr is that tests must pass. If you look at all recent PRs they have not done that

[meteorcloudy]

The postsubmit has been red like forever, which means all PRs will by default be red. https://buildkite.com/bazel/bazel-watcher/builds/3822

Also the project is still using Bazel 5, which has been deprecated with the Bazel 8 release.

[chickenandpork]

@alexeagle

https://bazel-contrib.github.io/SIG-rules-authors/hosting-policy.html#adding-criteria Criteria 9 is that this should work with bzlmod, #647 seems like maybe it still requires a WORKSPACE file.

#697 should alleviate the need for a WORKSPACE file

@meteorcloudy

[CI] has been red like forever, which means all PRs will by default be red. [...]

Also the project is still using Bazel 5, which has been deprecated with the Bazel 8 release.

We're making progress: CI went green with #710 (bumps to bazel-6.5.0) and is updating to 7.6.1 and bzlmod in #712 (we're working on educing the skipped tests there) to unblock a jump to 8.x

[github-actions[bot]]

Stale issue message

[chickenandpork]

With merge of #748 we get closer to requirements to migrate:

1. Passing tests
2. bzlmod
3. Bazel-7.6.1

#687 takes us to Bazel-8, which should (@alexeagle @achew22) unblock migration?

I seem to lack permission to check the “rebase” on #687, but if it rebases, I’ll take a look if @janwinkler1 doesn’t first

[janwinkler1]

@chickenandpork i started to look into upgrading to v8