gh release create: Fail when there are no new commits since the most recent release #6059

Describe the feature or problem you’d like to solve

Currently gh release create succeeds when there have been no new commits since the most recent release, creating a duplicate release. I would like gh release create to (optionally) fail when there have been no new commits since the most recent release.

Proposed solution

Add a new option that causes gh release create to fail when there have been no new commits since the most recent release.

Context

I created a duplicate release unintentionally when I hadn't noticed that there had been no new commits since the last release.

I now use a schedule GitHub action to create a new prerelease each night. It would create a duplicate release if there had been no new commits since the previous day.

Workaround

git fetch origin tag $(gh release list -L1 | cut -f1)
if git describe --tags --exact-match origin/master; then
  echo 'Error: No new commits since the most recent release'
  exit 1
else
  gh release create --prerelease --generate-notes $(date +%Y.%m.%d)
fi