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
I've integrated gql.tada into my project and it works perfectly locally. I've decided to keep my remote as clear of generated files as possible so I'm not committing the graphql-env.d.ts file generated, and instead am opting to generate it in my GitHub CI pipelines.
This seems to be caused by the GitHub Actions runner not reporting itself as a full TTY. If the command is not wrapped in a shell, then output piping will also not work correctly and be erroneously detected.
Writing to tadaOutputLocation is a default, so that's only done when the command is detected to not be piped to a non-TTY output. However, it seems that this never really works on GitHub, so we'll just have to disable piping detection via isTTY entirely (note: isatty returns the same result)
Describe the bug
I've integrated
gql.tada
into my project and it works perfectly locally. I've decided to keep my remote as clear of generated files as possible so I'm not committing thegraphql-env.d.ts
file generated, and instead am opting to generate it in my GitHub CI pipelines.However, just running
gql.tada generate output
in CI seems to print it out to the console and not look at the path I have setup in mytsconfig.json
. An example is this run; https://github.com/Tohaker/bioniQL/actions/runs/8938714273/job/24553391592Instead, setting the output on the command explicitly makes it work, as shown in this run; https://github.com/Tohaker/bioniQL/actions/runs/8938783801/job/24553588714
It's not a huge deal, but based on the documentation I expected the former to work as it does locally.
Reproduction
Tohaker/bioniQL#103
gql.tada version
1.6.3
Validations
The text was updated successfully, but these errors were encountered: