From 86ef1ea532d86c4b232821e0859e340d9128dafb Mon Sep 17 00:00:00 2001
From: David Davis <daviddavis@users.noreply.github.com>
Date: Thu, 31 Oct 2024 16:41:29 -0400
Subject: [PATCH] Update lock thread action timing (#182)

We're sometimes observing failures from this action and from the issue
below it seems like using a different random time might solve this.

https://github.com/dessant/lock-threads/issues/48
---
 .github/workflows/lock.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/lock.yml b/.github/workflows/lock.yml
index a8dd65c..e16d931 100644
--- a/.github/workflows/lock.yml
+++ b/.github/workflows/lock.yml
@@ -2,7 +2,7 @@ name: 'Lock Threads'
 
 on:
   schedule:
-    - cron: '0 0 * * *'
+    - cron: '33 2 * * *'
   workflow_dispatch:
 
 permissions: