Use bazel cquery to find out the binary path instead of guessing

.fasterci/config.yaml

@@ -15,6 +15,8 @@ workflows:
             - //...
           test_targets:
             - //...
+      - name: prer integration test
+        run: ./gitops/prer/prer_test.sh
       - name: Build & test e2e
         working-directory: e2e
         bazel:

BUILD.bazel

@@ -10,12 +10,8 @@
 
 # gazelle:build_tags darwin,linux
 # gazelle:exclude examples e2e
-# gazelle:proto disable_global
 # gazelle:go_naming_convention import_alias
 
-# gazelle:resolve go github.com/fasterci/rules_gitops/gitops/blaze_query //gitops/blaze_query:blaze_query
-# gazelle:resolve go github.com/fasterci/rules_gitops/gitops/analysis //gitops/analysis:analysis
-
 load("@buildifier_prebuilt//:rules.bzl", "buildifier")
 load("@gazelle//:def.bzl", "gazelle")
 

MODULE.bazel

@@ -29,7 +29,6 @@ use_repo(
     "io_k8s_api",
     "io_k8s_apimachinery",
     "io_k8s_client_go",
-    "org_golang_google_protobuf",
     "org_golang_x_oauth2",
     "org_golang_x_sync",
 )
@@ -53,17 +52,4 @@ kubeconfig(
 
 bazel_dep(name = "buildifier_prebuilt", version = "8.0.3", dev_dependency = True)
 
-bazel_dep(name = "rules_proto", version = "7.1.0")
-bazel_dep(name = "toolchains_protoc", version = "0.4.1")
 
-protoc = use_extension("@toolchains_protoc//protoc:extensions.bzl", "protoc")
-protoc.toolchain(
-    # Creates a repository to satisfy well-known-types dependencies such as
-    # deps=["@com_google_protobuf//:any_proto"]
-    google_protobuf = "com_google_protobuf",
-    # Pin to any version of protoc
-    version = "v27.1",
-)
-use_repo(protoc, "com_google_protobuf", "toolchains_protoc_hub")
-
-register_toolchains("@toolchains_protoc_hub//:all")

README.md

@@ -41,7 +41,7 @@ copy the MODULE.bazel snippet into your `MODULE.bazel` file.
 
 ### Prerequisites
 
-* **Git**: A minimum Git version of **2.19.0** is required for runtime operations due to the use of partial clones (`--filter=blob:none`) and other modern clone/fetch options (e.g. `--no-tags`). If you are running the test suite, Git **2.28.0** or later is required due to test dependencies (specifically `git init --initial-branch`).
+* **Git**: A minimum Git version of **2.19.0** is required for runtime operations due to the use of partial clones (`--filter=blob:none`) and other modern clone/fetch options (e.g. `--no-tags`).
 
 
 <a name="k8s_deploy"></a>
@@ -434,6 +434,8 @@ The `--release_branch` specifies the value of the ***release_branch_prefix*** at
 
 To handle potential race conditions (e.g., if a deployment branch is merged and deleted on the remote server while the tool is running), the `--push_retry_max` flag can be set (defaults to `2`). It will retry cloning/checking out the repository, manifest rendering, committing, and pushing up to the configured limit if the git push fails because of a mismatch (e.g. branch deleted or updated on remote).
 
+The `--git_timeout` flag can be used to configure a timeout for Git operations (defaults to `5m`). If any Git operation (like clone, checkout, fetch, commit, or push) exceeds this duration, the execution will fail immediately.
+
 The `create_gitops_prs` tool will query all `gitops` targets which have set the ***deploy_branch*** attribute (see [k8s_deploy](#k8s_deploy)) and the ***release_branch_prefix*** attribute value that matches the `release_branch` parameter.
 
 In case you need to specify a custom Bazel flag during the pull request process, you can add one `--bazel_flag` such as `--bazel_flag --config=ci` or multiple such as `--bazel_flag --config=ci --bazel_flag --color=no`.

WORKSPACE

@@ -0,0 +1 @@
+# Marker file for workspace root (required for older Bazelisk/tooling compatibility)

e2e/WORKSPACE

@@ -0,0 +1 @@
+# Marker file for workspace root (required for older Bazelisk/tooling compatibility)