loopbackio / loopbackio/loopback-next
CI builds for Windows via GitHub Actions
@achrinza is already working on this.
Since Jan 7, 2021.
- Dominant language
- TypeScript
- Stars
- 5.1k
- Forks
- 1.1k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 27
Description
This is a follow-up for https://github.com/strongloop/loopback-next/pull/5110, where we configured CI builds to run on GitHub Actions, but did not manage to pass all tests on Windows.
My current understanding is that GitHub Actions is running CI scripts with non-TTY (and possibly empty) `stdin` stream, thus triggering TTY-related issues as described in https://github.com/strongloop/loopback-next/issues/4425#issuecomment-578059551 and follow-up comments. The discussion further continues in #4607, which is the issue tracking this specific problem.
In #5110, @achrinza added https://github.com/Yuri6037/Action-FakeTTY to our workflow to enable a fake TTY. This fixed the problem on MacOS, but not for Windows :(
We need to further investigate this problem and either find a way how to setup TTY or fix #4607.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.