-
Notifications
You must be signed in to change notification settings - Fork 4
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
c: add unittest CI #18
Conversation
In the already existing eslint configuration file, rules is set with warn. if it is not an error, it cannot be detected by ci, is it doesn’t problem? |
I don't know. Maybe it is setted as you said. But I don't know how can CI ignore this errors. |
uses: actions/setup-node@v3 | ||
with: | ||
node-version: '16' | ||
- run: if [ ! -x "$(command -v yarn)" ]; then npm install -g yarn; fi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not familiar with self-hosted runner.
Isn't there a problem if I install yarn directly on a self-hosted machine?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general, I know that when we execute setup-node
action, yarn
is also installed. But, it was not actually installed, so I installed it directly.
relate: #6
This ci of github action execute all unittest.