denied: Resource not accessible by integration

[dalton-cole]

When using the docker push starter workflow, exactly as-is from this repo, I get: denied: Resource not accessible by integration at the end of the push step. It had worked in the past but now it does not. Would my auto-generated token have somehow lost access to an existing package?

[dalton-cole]

If I create a personal access token and use that instead of piping in the GITHUB_TOKEN, the push works.

[ktori]

Having the same issue with a workflow that worked before for several weeks, failing on docker push now.

[dalton-cole]

@ktori as I mentioned above, if you create a personal access token with the right permissions, you can substitute that in via action secrets for now.

[ktori]

@ktori as I mentioned above, if you create a personal access token with the right permissions, you can substitute that in via action secrets for now.

I can't access the secrets in that project, sadly

[ktori]

I contacted GitHub Support and they have resolved this issue in my repo, @dalton-cole if this was a site-wide issue it should be resolved for you too now.

[eine]

@ktori, I can confirm that it is fixed for me now. It worked for several months, it was failing during the last couple of days, but restarting the failed jobs now did work. Thanks for commenting about it!

[dalton-cole]

Issue appears to be resolved! Thanks @ktori and @eine for letting me know!

[glenn-jocher]

Seeing this error currently on PR greetings. Anytime someone submits a PR this happens:

[vincerubinetti]

This is happening to me, seemingly out of no where (it seemed to be working just yesterday). actions/configure-pages#40

Creating a PAT is an unacceptable solution for me, as 1) PATs have very broad permissions, 2) it defeats the purpose of me running an Action to enable GitHub Pages: to do something automatically.

[Hamza5]

As today in late 2023 (2023-12-09), this issue is still happening (and undocumented), and creating a Personal Access Token with write access to GitHub Pages is the solution for now.

This is how I implemented in in my workflow that builds a Flutter Web app and hosts it on GitHub Pages on every push:

name: CI/CD
on:
  push
jobs:
  Build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v4
      - name: Install Flutter
        uses: subosito/flutter-action@v2
        with:
          flutter-version: '3.13.x'
          channel: 'stable'
          cache: true
          cache-key: 'flutter-:os:-:channel:-:version:-:arch:'
      - name: Install Flutter packages
        run: flutter pub get
      - name: Configure GitHub Pages
        id: pages
        uses: actions/configure-pages@v4
        with:
          token: ${{ secrets.PAGES_TOKEN }}
      - name: Build the Web app
        run: flutter build web --base-href="${{ steps.pages.outputs.base_path }}/" --dart-define=OWM_API_KEY=${{ secrets.OWM_API_KEY }}
      - name: Upload the Web app
        uses: actions/upload-pages-artifact@v2
        with:
          path: ./build/web
  Deploy:
    runs-on: ubuntu-latest
    needs: Build
    permissions:
      contents: read
      pages: write
      id-token: write
    concurrency:
      group: "pages"
      cancel-in-progress: false
    environment:
      name: github-pages
      url: ${{steps.deployment.outputs.page_url}}
    steps:
      - name: Deploy the Web app
        id: deployment
        uses: actions/deploy-pages@v3

PAGES_TOKEN is a Personal Access Token that has writing permession to Pages.