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
Resource not accessible by integration for the default token, the action is green nevertheless #1350
Comments
I believe you need to add the permission block to the steps section on any new workflows which is due to GitHub recent increased security to GitHub Actions. permissions:
# write permission is required to create a github release
contents: write
# write permission is required for autolabeler
# otherwise, read permission is required at least
pull-requests: write |
The thing is that it was an old workflow that actually worked before... and works now. So ther ewas a temporary glitch somewhere. @jetersen what do you think about failing the action by default if a request fails? |
Nevertheless, I confirm it fixes the issue itself |
I have a similar issue when not providing the token, the action is green but when you inspect the RD step then you see the error there, would help if these errors fail the action. |
Hi, name: Release Drafter
on:
workflow_dispatch:
pull_request:
push:
branches:
- main
permissions:
contents: write
pull-requests: write
jobs:
update_release_draft:
runs-on: ubuntu-latest
steps:
- uses: release-drafter/release-drafter@v6
with:
disable-releaser: github.ref != 'refs/heads/main'
config-name: release-drafter.yml
commitish: main
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} which results to green check, but errors inside:
|
I hit a weird behavior in https://github.com/wiremock/wiremock-testcontainers-go that has lasted since a few days ago
@v5
of the action, similarly to all other repositories where the action runs successfully: https://github.com/wiremock/wiremock-testcontainers-go/blob/main/.github/workflows/changelog-draft.ymlAny ideas about what's wrong with this repo would be appreciated. I also suggest failing the action by default in the case of such errors.
Action view
Execution log
The text was updated successfully, but these errors were encountered: