Skip to content

Commit e7950f6

Browse files
committed
Ops: GitHub release page fix [skip ci]
Each release was showing something odd for commits, for example: released this 9 days ago · 0 commits to 7cfce4bfc7eaafce8c79749633a38df6c6479529 since this release The GitHub docs say I shouldn't need to specify commitish for a release, but it seems I do, at least for the way I am releasing. Verified on test-doc-blocks and carried over here. Commits oddity should no longer appear for next releases.
1 parent 01fa1e5 commit e7950f6

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

.github/workflows/release.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -75,3 +75,4 @@ jobs:
7575
with:
7676
tag_name: ${{ steps.target-version.outputs.tag}}
7777
release_name: ${{ steps.target-version.outputs.tag}}
78+
commitish: main

0 commit comments

Comments
 (0)