You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I want to generate types for my storyblok project using the storyblok cli. In order to have my types in sync I want to create a github action that generates types on every PR.
Current behavior:
Currently I am having issues using the storyblok cli in my github action.
When I run the action listed below, my workflow throws the following error:
Hi, welcome to the Storyblok CLI
? Enter your email address:
Error: Process completed with exit code 130.
When I run the same command from my local terminal everything seems to work.
Looks like in a CI/CD env the --token flag does not skip the prompt
Expected behavior:
Running the storyblok cli for generating types works in a CI/CD env the same way as it does in a local env.
I was not able to find an example, guide or documentation how to use the cli in a CI/CD env, thats's why I opend this issue.
Thanks in advance for your support :)
The text was updated successfully, but these errors were encountered:
Hello, I want to generate types for my storyblok project using the storyblok cli. In order to have my types in sync I want to create a github action that generates types on every PR.
Current behavior:
Currently I am having issues using the storyblok cli in my github action.
When I run the action listed below, my workflow throws the following error:
When I run the same command from my local terminal everything seems to work.
Looks like in a CI/CD env the --token flag does not skip the prompt
Expected behavior:
Running the storyblok cli for generating types works in a CI/CD env the same way as it does in a local env.
Steps to reproduce:
https://github.com/christophsaile/next-storyblok
Related code:
I was not able to find an example, guide or documentation how to use the cli in a CI/CD env, thats's why I opend this issue.
Thanks in advance for your support :)
The text was updated successfully, but these errors were encountered: