From a5def9999c4caa19a54c143ff3be772a40d0448e Mon Sep 17 00:00:00 2001
From: Takashi Kokubun <takashikkbn@gmail.com>
Date: Thu, 9 Oct 2025 21:24:26 -0700
Subject: sync_default_gems.yml: Experiment with fetch-depth: 1

At the moment, we're not sure which gem relies on past renames. So we
try this, and revert it if it turns out to be necessary.

Given that it slows down every single sync, however, I'm thinking of
making tool/sync_default_gems.rb responsible for implementing all
necessary renames on cherry-picks using filter-branch (or any
modification on commits before pushing them).
---
 .github/workflows/sync_default_gems.yml | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/.github/workflows/sync_default_gems.yml b/.github/workflows/sync_default_gems.yml
index 3912f567e3..3a811be18a 100644
--- a/.github/workflows/sync_default_gems.yml
+++ b/.github/workflows/sync_default_gems.yml
@@ -30,12 +30,8 @@ jobs:
       - uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
         name: Check out ruby/ruby
         with:
-          fetch-depth: 999999 # Fetch all history to follow past renames. Not using 0 to avoid fetching tags/branches.
           token: ${{ github.repository == 'ruby/ruby' && secrets.MATZBOT_AUTO_UPDATE_TOKEN || secrets.GITHUB_TOKEN }}
 
-      - name: Increase rename limit
-        run: git config merge.renameLimit 999999
-
       - name: Run tool/sync_default_gems.rb
         id: sync
         run: |
-- 
cgit v1.2.3