Fix: Move the git fetch depth 43/72343/1
authorAndrew Grimberg <agrimberg@linuxfoundation.org>
Mon, 6 Nov 2023 22:58:21 +0000 (14:58 -0800)
committerAndrew Grimberg <agrimberg@linuxfoundation.org>
Mon, 6 Nov 2023 23:30:48 +0000 (15:30 -0800)
It is not possible to specify a depth larger than 1 with the tag
checkout that is performed. Move the depth increase to where it's
actually needed.

Issue: RELENG-4973
Signed-off-by: Andrew Grimberg <agrimberg@linuxfoundation.org>
Change-Id: I394c2359f8d8e8fec83bf5b39a9282222a9c2ad5

.github/workflows/release.yaml

index e2fd7a8..17b0485 100644 (file)
@@ -11,9 +11,6 @@ jobs:
     steps:
       - name: Checkout repository
         uses: actions/checkout@v4
-        with:
-          fetch-depth: 30
-          fetch-tags: true
       - name: Configure Python
         uses: actions/setup-python@v4
         with:
@@ -57,7 +54,9 @@ jobs:
             Cheers,
             LF Release Engineering
       - name: Generate reno report
-        run: >-
+        run: |
+          # fetch last 30 changes
+          git fetch --depth=30
           pipx run tox -e reno -- report \
             --version "${{ steps.tag.outputs.tag }}" \
             2>/dev/null > reno-notes.md || true
@@ -73,7 +72,7 @@ jobs:
             sed '1d' > modified-reno-notes.md
           fi
       - name: Create Release Notes
-        run: >-
+        run: |
           gh release create ${{ steps.tag.outputs.tag }} --generate-notes \
             -F modified-reno-notes.md
         env: