Closed kazupon closed 4 years ago
Hi @kazupon Actually this is bug in github actions that fixed in current version, but as I see you run v1 actions https://github.com/kazupon/poeditor-service-provider/blob/master/.github/workflows/release.yml#L14-L15
All work nice with latest version of github actions https://github.com/jeetiss/try-shipjs/commit/dc141c3bda63f5ff68a868458f71ed90c9510522/checks?check_suite_id=388868397
If you wanna use v1 actions, you can add custom secret GH_TOKEN
and replace original token with them in actions as workaround:
- run: npm run release:trigger
env:
GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
@jeetiss
Thanks!
I'll try to it with master
version, when I'll plan to release. :)
Describe the bug Unfortunately,
GITHUB_TOKEN
cannot be used to authenticate git commands: In my github action workflow, it could not release withrelease:trigger
. 😞The following error occurred in the GitHub action workflow:
See the https://github.com/kazupon/poeditor-service-provider/runs/377176890
To Reproduce Steps to reproduce the behavior:
release:prepare
(https://github.com/kazupon/poeditor-service-provider/pull/36)release
release:trigger
(https://github.com/kazupon/poeditor-service-provider/commit/3dace81b5cc45dbf16e8b56758e027104d37c43b/checks?check_suite_id=387723670)Environment (please complete the following information):
node -v
:10.x
yarn -v
:1.19.2
0.13.1
Additional context