Hi, On Thu, 25 Nov 2021, Matthias Aßhauer wrote: > On Thu, 25 Nov 2021, Mahdi Hosseinzadeh via GitGitGadget wrote: > > > diff --git a/.github/workflows/create-release.yml > > b/.github/workflows/create-release.yml > > new file mode 100644 > > index 00000000000..711ba105e42 > > --- /dev/null > > +++ b/.github/workflows/create-release.yml > > @@ -0,0 +1,40 @@ > > +name: Create GH release > > + > > +# Create a GitHub release for each new tag. > > +# The release notes are taken from the release notes file > > +# modified in that commit located in Documentation/RelNotes directory. > > + > > +on: > > + push: > > + tags: > > + - v[0-9]+.* > > [...] > > All in all I think this is too convoluted for what it's trying to > achieve. I think we should be able to achieve the same result with > something like this: > > .github/workflows/create-release.yml | 37 ++++++++++++++++++++++++++++ > 1 file changed, 37 insertions(+) > create mode 100644 .github/workflows/create-release.yml > > diff --git a/.github/workflows/create-release.yml > b/.github/workflows/create-release.yml > new file mode 100644 > index 0000000000..5b9fdf0372 > --- /dev/null > +++ b/.github/workflows/create-release.yml > @@ -0,0 +1,37 @@ > +name: Create GH release > + > +# Create a GitHub release for each new tag. > +# The release notes are taken from the release notes file > +# modified in that commit located in Documentation/RelNotes directory. > + > +on: > + push: > + tags: > + - v[0-9]+.[0-9]+.[0-9]+ > + > +permissions: > + contents: write > + > +jobs: > + create-gh-release: > + name: Create a new release or update an existing release in the GitHub > repository > + runs-on: ubuntu-latest > + steps: > + - name: Checkout the repository > + uses: actions/checkout@v2 > + with: > + fetch-depth: 1 > + - name: Get version number > + shell: bash > + run: | > + echo GIT_VERSION=${GITHUB_REF#refs/tags/v} >> $GITHUB_ENV > + - name: Create the release > + uses: actions/create-release@v1 > + env: > + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} > + with: > + tag_name: ${{ github.ref_name }} > + release_name: ${{ github.ref_name }} > + body_path: Documentation/RelNotes/${{ env.GIT_VERSION }}.txt > + draft: false > + prerelease: false > -- > 2.25.1 > > An example of the result this reduced action produces can be found at [4] > (release notes for v2.34.1, but the tagged commit isn't v2.34.1). > > Best regards > > Matthias > > [1] https://github.com/git/git/pull/1146 > [2] https://github.com/git/git/pull/1146#discussion_r756854259 > [3] https://github.com/git/git/pull/1146#discussion_r756845042 > [4] https://github.com/rimrul/git/releases/tag/v2.34.1 One thing I had not thought of earlier: do we really want to do this in every fork of git/git? I know for a fact that microsoft/git has a very different workflow upon pushing a tag. So maybe we need something like this, too: create-gh-release: + if: github.repository == 'git/git' name: Create a new release or update an existing release in the GitHub repository Ciao, Dscho