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
Copy file name to clipboardexpand all lines: README.md
+11-11
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,12 @@
1
-
# GitHub ESLint runner
1
+
# GitHub Jest runner
2
2
3
3
This action executes Jest test runner without any previous action/build step or Docker required.
4
4
5
5
## Prerequisites
6
6
7
7
### Jest
8
-
You must have the ESLint running locally for the action to execute. It will use the same rules as you do locally.
9
-
More info [on the ESLint getting started guide](https://eslint.org/docs/user-guide/getting-started#installation-and-usage)
8
+
You must have the Jest running locally for the action to execute.
9
+
More info [on the Jest getting started guide](https://jestjs.io/docs/en/getting-started)
10
10
11
11
## Usage
12
12
@@ -16,24 +16,24 @@ This is the simplest example to get it running:
16
16
```
17
17
workflow "New workflow" {
18
18
on = "push"
19
-
resolves = ["ESLint"]
19
+
resolves = ["Jest"]
20
20
}
21
21
22
-
action "ESLint" {
23
-
uses = "stefanoeb/eslint-action@master"
22
+
action "Jest" {
23
+
uses = "stefanoeb/jest-action@master"
24
24
}
25
25
```
26
26
27
-
By default it will run ESLint through all the files in the project. But you can also specify a glob of files on the `args`, just like ESLint:
27
+
By default it will run Jest on all the test files in the project. But you can also specify a glob of files on the `args`, just like on the Jest CLI, as well as options:
0 commit comments