EndBug / add-and-commit

:octocat: Automatically commit changes made in your workflow run directly to your repo
MIT License
1.12k stars 115 forks source link

It doesn't work for me #583

Closed razb-viola closed 8 months ago

razb-viola commented 9 months ago

No matter what I did, it just didn't create a new commit, either on the pushed branch or on new branch.

My repo is a repo under organization, but I checked the Read and Write permissions..

EndBug commented 9 months ago

Hi, please link your workflow and the failing action run

razb-viola commented 9 months ago

Sure here it is:

name: Tag and Release
on:
  push:
    branches:
      - main1
jobs:
  build:
    runs-on: ubuntu-latest
    permissions:
      contents: write
    steps:
      - uses: actions/checkout@v4

      - name: Bump version and push tag
        id: tag_version
        uses: mathieudutour/github-tag-action@v6.1
        with:
          github_token: ${{ secrets.GITHUB_TOKEN }}
          tag_prefix: ''

      - name: Echo the tag
        run: echo "Tag name ${{ steps.tag_version.outputs.new_tag }}"

      - name: Echo the changelog
        run: echo "Tag name ${{ steps.tag_version.outputs.changelog }}"

      - name: Echo package.json
        run: cat package.json

      - name: Configure node
        uses: actions/setup-node@v4
        with:
          node-version: '21.1.0'
          registry-url: 'https://registry.npmjs.org'

      - name: Tell who we are to npm
        run: |
          git config --global user.email "actions@github.com"
          git config --global user.name "Github Actions"

      - name: Update package.json version
        run: npm version ${{ steps.tag_version.outputs.new_tag }}
        env:
          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

      - name: Echo package.json after update
        run: cat package.json

      - uses: EndBug/add-and-commit@v9

      - name: Publish to NPM registry
        run: npm publish --access=public
        env:
          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
EndBug commented 9 months ago

and the failing action run

I can't help you if I don't see the logs and the error you're talking about. Can you please send a link to the failing action run?

razb-viola commented 9 months ago

Oh the problem is that the action is not failing. It completes however I don't see the new commit in the merged branch. You know what, let me test this again and if I catch any errors, maybe hidden in the logs or something I will let you know.

github-actions[bot] commented 8 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.