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
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ In general, integrating Coderrect requires two steps:
30
30
2. Apply Coderrect Github Action
31
31
```yaml
32
32
- name: Coderrect Scan
33
-
uses: coderrect-inc/coderrect-github-action@v0.6
33
+
uses: coderrect-inc/coderrect-github-action@v1.0
34
34
```
35
35
36
36
### For CMake projects
@@ -47,7 +47,7 @@ Since we are building the project under the `build` directory instead of the roo
47
47
We will also need to specify the build directory for Coderrect.
48
48
```yaml
49
49
- name: Coderrect Scan
50
-
uses: coderrect-inc/coderrect-github-action@v0.6
50
+
uses: coderrect-inc/coderrect-github-action@v1.0
51
51
with:
52
52
buildPath: "build"
53
53
```
@@ -63,7 +63,7 @@ You will need to install the fortran compiler first. For example:
63
63
Then it is likely that you need to specify the fortran compiler when you use `make`. If so, you should also pass the full compilation command to Coderrect. (`gcc` is pre-installed in the Github Action environment.)
@@ -76,7 +76,7 @@ Coderrect allows you to provide a configuration file to fully customize your ana
76
76
In order to do so, check our [documentation](https://coderrect.com/documentation/reference/) to see available configurations. Once you write a configuration file (say `coderrect.json`). You can pass it to the scanner as below:
0 commit comments