Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Push issue, 403 error #55

Closed
slinden2 opened this issue May 22, 2020 · 8 comments
Closed

Push issue, 403 error #55

slinden2 opened this issue May 22, 2020 · 8 comments

Comments

@slinden2
Copy link

Out of the blue today my workflow stopped working at push to repo step.

It gives me the following error:

Run ad-m/github-push-action@master
Started: bash /home/runner/work/_actions/ad-m/github-push-action/master/start.sh
Push to branch master
remote: Permission to ***/sunday-night-wreckfest.git denied to github-actions[bot].
fatal: unable to access 'https://github.com/***/sunday-night-wreckfest.git/': The requested URL returned error: 403
Error: Invalid status code: 128
    at ChildProcess.<anonymous> (/home/runner/work/_actions/ad-m/github-push-action/master/start.js:9:19)
    at ChildProcess.emit (events.js:210:5)
    at maybeClose (internal/child_process.js:1021:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5) {
  code: 128
}
Error: Invalid status code: 128
    at ChildProcess.<anonymous> (/home/runner/work/_actions/ad-m/github-push-action/master/start.js:9:19)
    at ChildProcess.emit (events.js:210:5)
    at maybeClose (internal/child_process.js:1021:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)

I have use the same workflow without changes for a couple of weeks and today I suddenly started encountering this problem.

Here's also my workflow:

name: Test and Deploy
on:
  push:
    branches: [master]
  pull_request:
    branches: [master]

jobs:
  build:
    runs-on: ubuntu-latest
    env:
      working-directory-be: ./backend
      working-directory-fe: ./frontend
      GS_PRIVATE_KEY: ${{ secrets.GS_PRIVATE_KEY }}
      GS_SERVICE_ACCOUNT_EMAIL: ${{ secrets.GS_SERVICE_ACCOUNT_EMAIL }}

    steps:
      - uses: actions/checkout@v2
      - name: Use Node.js
        uses: actions/setup-node@v1
        with:
          node-version: 12.x
      - name: Install backend dependencies
        run: npm install
        working-directory: ${{ env.working-directory-be }}
      - name: Run tests
        run: npm test
        working-directory: ${{ env.working-directory-be }}
        env:
          CI: true
      - name: Build backend
        run: npm run build:server
        working-directory: ${{ env.working-directory-be }}
      - name: Install frontend dependencies
        run: npm install
        working-directory: ${{ env.working-directory-fe }}
      - name: Build frontend
        run: npm run build
        working-directory: ${{ env.working-directory-fe }}
      - name: Create production bundle
        run: |
          mkdir -p ./dist
          cp -r ./backend/build/. ./dist
          cp -r ./frontend/build/. ./dist/client
          rm -r ./backend/build/
          rm -r ./frontend/build/
          cp ./backend/package.json ./dist/package.json
          cp ./backend/package-lock.json ./dist/package-lock.json
          cp ./backend/Procfile ./dist/Procfile
      - name: Commit production bundle
        run: |
          git config --global user.name '${{ secrets.USERNAME }}'
          git config --global user.email '${{ secrets.USERNAME }}@users.noreply.github.com'
          git add .
          git commit -m "Automated production bundle creation"
      - name: Push production bundle to repo
        uses: ad-m/github-push-action@master
        with:
          github_token: ${{ secrets.GITHUB_TOKEN }}
      - name: Push production bundle to dokku
        uses: slinden2/dokku-deploy-github-action@v1.1-alpha
        with:
          ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY }}
          dokku-ip-address: ${{ secrets.SERVER_IP }}
          dokku-host: ***
          app-name: ***
          git-subtree-prefix: "dist"
          force-push-subtree: "true"

@theapache64
Copy link

theapache64 commented May 22, 2020

Same with me too.. It was working fine @ad-m @slinden2

@frolovdev
Copy link

Good day, same here

image

Error:

Run ad-m/github-push-action@master
  with:
    github_token: ***
    branch: master
    directory: .
Started: bash /home/runner/work/_actions/ad-m/github-push-action/master/start.sh
Push to branch master
remote: Permission to frolovdev/npm-canary.git denied to github-actions[bot].
fatal: unable to access 'https://github.com/frolovdev/npm-canary.git/': The requested URL returned error: 403
Error: Invalid status code: 128
    at ChildProcess.<anonymous> (/home/runner/work/_actions/ad-m/github-push-action/master/start.js:9:19)
    at ChildProcess.emit (events.js:210:5)
    at maybeClose (internal/child_process.js:1021:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5) {
  code: 128
}
Error: Invalid status code: 128
    at ChildProcess.<anonymous> (/home/runner/work/_actions/ad-m/github-push-action/master/start.js:9:19)
    at ChildProcess.emit (events.js:210:5)
    at maybeClose (internal/child_process.js:1021:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)

@chrislopez24
Copy link

Same error, worked fine before

@theapache64
Copy link

@chrislopez24 @frolovdev @slinden2 @ad-m

I think this issue is not related to this repo ('github-push-action'). I tried with manual pushing (using access token with set-url), then also am getting 403. I believe GitHub might have changed something.

@frolovdev
Copy link

frolovdev commented May 22, 2020

@theapache64 @chrislopez24
Maybe related to our problem
https://www.githubstatus.com/

image

@theapache64
Copy link

Ohh I see. Possibly this might be the issue.

@slinden2
Copy link
Author

It has been fixed for me. Closing the issue.

@theapache64
Copy link

theapache64 commented May 23, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants