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
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -135,10 +135,11 @@ First, [create a new file](https://docs.github.com/en/repositories/working-with-
135
135
136
136
| Name | Required | Description |
137
137
| ----- | -------- | ----------- |
138
-
|`result_file`| yes | The file that contains the results. |
139
-
|`result_format`| yes | The format in which to store the results [json \| sarif]. For GitHub's scanning dashboard, select `sarif`. |
138
+
|`results_file`| yes | The file that contains the results. |
139
+
|`results_format`| yes | The format in which to store the results [json \| sarif]. For GitHub's scanning dashboard, select `sarif`. |
140
140
|`repo_token`| no | PAT token with repository read access. Follow [these steps](/docs/authentication/fine-grained-auth-token.md) to create it. |
141
141
|`publish_results`| recommended | This will allow you to display a badge on your repository to show off your hard work. See details [here](#publishing-results).|
142
+
| `file_mode` | no | The method to fetch files from the repository: `archive` or `git` (default `archive`).
142
143
143
144
### Publishing Results
144
145
The Scorecard team runs a weekly scan of public GitHub repositories in order to track
0 commit comments