-
-
Notifications
You must be signed in to change notification settings - Fork 591
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
chore(workflows): add macOS, Windows, node v13 and linting #1356
Conversation
.github/workflows/nodejs.yml
Outdated
run: | | ||
yarn | ||
yarn bootstrap | ||
- name: Run test for webpack version ${{ matrix.webpack-version }} | ||
- name: Linting | ||
run: yarn lint |
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.
Let's move it to own step, we don't need run link on every platform and node version
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.
We need to integrate GitHub actions with webpack-bot
if we are removing travis.
@evilebottnawi Thanks for your update. I labeled the Pull Request so reviewers will review it again. @rishabh3112 Please review the new changes. |
From slack:
So let's merge, I don’t think that the bot helps us so much, we see everything that comes from without a bot |
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.
Okay, But I still insist to have it as soon as possible because the webpack-bot
is the first point of interaction with the person who puts up the PR. It let's them know about they have to sign CLA, whether their PR passed the checks, etc which really help those who are new to project and don't know where are these things.
For us reviewers, I can confirm that without bot too we are fine.
1cf5c4f
to
18c0d5a
Compare
18ce59f
to
2dc0ed4
Compare
May I ask what are you trying to do exactly? I see a lot of commits trying to skip tests. |
@fokusferit Investigate why |
a6ce40c
to
ff645d3
Compare
@evilebottnawi The tests look fine, but there are code style issue in your Pull Request. Please review the following:
See complete report here. |
Merging, feel free to feedback, in the next PRs, I will setup coverage normally |
What kind of change does this PR introduce?
GitHub workflow changes
next - #1355