Skip to content

Commit

Permalink
Fix: Move the git fetch depth
Browse files Browse the repository at this point in the history
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
  • Loading branch information
tykeal committed Nov 6, 2023
1 parent 712e20a commit 44c6ad1
Showing 1 changed file with 4 additions and 5 deletions.
9 changes: 4 additions & 5 deletions .github/workflows/release.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down Expand Up @@ -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
Expand All @@ -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:
Expand Down

0 comments on commit 44c6ad1

Please sign in to comment.