Tagging workflow broken

[baynezy]

Why are you starting this discussion?

Product Feedback

What GitHub Actions topic or product is this about?

General

Discussion Details

Whenever a PR is merged into my default branch develop, a GitHub action is triggered.

name: Deploy Develop Branch

on:
  push:
    branches:
      - develop
    paths:
      - 'src/**'
      - 'test/**'
      - '**.sln'
      - '**.cake'
      - '.github/workflows/branch-develop.yml'
      - '.github/workflows/step-*.yml'
  workflow_dispatch:

permissions:
  checks: write
  pull-requests: write
  contents: write

jobs:
  get-version:
    uses: ./.github/workflows/step-version.yml
    with:
      is-pre-release: true

  build:
    needs: [ get-version ]
    uses: ./.github/workflows/step-build.yml
    with:
      version: ${{ needs.get-version.outputs.version }}
      checkout-ref: ${{ github.base_ref }}

  publish-to-nuget:
    needs: [ get-version,build ]
    uses: ./.github/workflows/step-publish.yml
    secrets:
      nuget-api-key: ${{ secrets.NUGET_API_KEY }}
    with:
      deploy-env: nuget-beta
      deploy-branch: ${{ github.base_ref }}
      version: ${{ needs.get-version.outputs.version }}
  
  tag-release:
    needs: [ get-version,publish-to-nuget ]
    uses: ./.github/workflows/step-tag-release.yml
    with:
      version: ${{ needs.get-version.outputs.version }}

This will work perfectly fine unless a workflow file was modified in the PR that triggered the workflow. In that case, the final job fails:

Run git config --global user.name "GitHub Action Bot"
  git config --global user.name "GitHub Action Bot"
  git config --global user.email "[email protected]"
  git tag -a $VERSION -m "Version $VERSION created via GitHub Actions"
  git push origin $VERSION
  shell: /usr/bin/bash -e {0}
  env:
    VERSION: 1.1.0.14-beta
To https://github.com/baynezy/StubLogger
 ! [remote rejected] 1.1.0.14-beta -> 1.1.0.14-beta (refusing to allow a GitHub App to create or update workflow `.github/workflows/step-build.yml` without `workflows` permission)
error: failed to push some refs to 'https://github.com/baynezy/StubLogger'
Error: Process completed with exit code 1.

The code for that final job is as follows:

on:
  workflow_call:
    inputs:
      version:
        required: true
        description: 'Version to deploy'
        type: string

permissions:
  contents: write
  
jobs:
  tag:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v5
      - name: Create tag
        env:
          VERSION: ${{ inputs.version }}
        run: |
          git config --global user.name "GitHub Action Bot"
          git config --global user.email "[email protected]"
          git tag -a $VERSION -m "Version $VERSION created via GitHub Actions"
          git push origin $VERSION

This is incredibly annoying, as I see no reason why I cannot tag on a push on a protected branch that was triggered by a PR approval.

How can I resolve this?

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐