From e05411140ddf85ee5f916655c77f4f50fbb12d9b Mon Sep 17 00:00:00 2001 From: Ashwin Bhat Date: Sat, 9 Aug 2025 10:58:52 -0700 Subject: [PATCH] Remove timeout-minutes from lock-closed-issues workflow (#5455) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The 10-minute timeout is unnecessary for this workflow as it typically completes quickly. Removing it allows the workflow to use the default GitHub Actions timeout (6 hours for public repos, 72 hours for private), providing more flexibility if the workflow needs to process a large number of issues. Also fixed trailing whitespace inconsistencies in the script. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-authored-by: Claude --- .github/workflows/lock-closed-issues.yml | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/.github/workflows/lock-closed-issues.yml b/.github/workflows/lock-closed-issues.yml index 3cffd907..3b353332 100644 --- a/.github/workflows/lock-closed-issues.yml +++ b/.github/workflows/lock-closed-issues.yml @@ -15,7 +15,6 @@ concurrency: jobs: lock-closed-issues: runs-on: ubuntu-latest - timeout-minutes: 10 steps: - name: Lock closed issues after 7 days of inactivity uses: actions/github-script@v7 @@ -23,13 +22,13 @@ jobs: script: | const sevenDaysAgo = new Date(); sevenDaysAgo.setDate(sevenDaysAgo.getDate() - 7); - + const lockComment = `This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.`; - + let page = 1; let hasMore = true; let totalLocked = 0; - + while (hasMore) { // Get closed issues (pagination) const { data: issues } = await github.rest.issues.listForRepo({ @@ -89,5 +88,5 @@ jobs: page++; } - + console.log(`Total issues locked: ${totalLocked}`);