From 0e771187454687f12e5688bfe362fa1e29fa77a2 Mon Sep 17 00:00:00 2001
From: "Ian (Hee) Cha" <heec@google.com>
Date: Sun, 24 Dec 2023 18:17:29 -0800
Subject: [PATCH] [Please ignore] Lockfile testing for Automation (#20672)

This is to test whether it's possible to update the lockfile and push
the changes to anoter person's branch in their own forked repo.
---
 .github/workflows/update-lockfiles.yml | 27 ++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)
 create mode 100644 .github/workflows/update-lockfiles.yml

diff --git a/.github/workflows/update-lockfiles.yml b/.github/workflows/update-lockfiles.yml
new file mode 100644
index 00000000000000..b0580ed2653cec
--- /dev/null
+++ b/.github/workflows/update-lockfiles.yml
@@ -0,0 +1,27 @@
+name: Update Lockfile
+
+on:
+  pull_request:
+    types:
+      - labeled
+
+env:
+  GH_TOKEN: ${{ secrets.BAZEL_IO_TOKEN }}
+
+jobs:
+  update-lockfile:
+    runs-on: ubuntu-latest
+    if: contains(github.event.label.name, 'updatelock')
+    steps:
+      - name: Check out code
+        uses: actions/checkout@v2
+      - name: Install bazelisk
+        run: |
+          curl -LO "https://github.com/bazelbuild/bazelisk/releases/download/v1.19.0/bazelisk-linux-amd64"
+          mkdir -p "${GITHUB_WORKSPACE}/bin/"
+          mv bazelisk-linux-amd64 "${GITHUB_WORKSPACE}/bin/bazel"
+          chmod +x "${GITHUB_WORKSPACE}/bin/bazel"
+      - name: Run cherrypicker on comment
+        uses: iancha1992/continuous-integration/actions/lockfile-test
+        with:
+          github-dir: ${{ GITHUB_WORKSPACE }}/bin/bazel