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
+10-4
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,8 @@ If the `checkUser` option is enabled, `forker` will check the specified GitHub o
11
11
12
12
For legal and compliance reasons, organizations or individuals can choose to provide an optional `licenseAllowlist` to compare against the [license of the repository](https://docs.github.com/en/rest/reference/licenses) being forked. If the license key returned by the GitHub API is not found within the provided allowlist, `forker` will exit without forking the repository, and display an error.
13
13
14
+
---
15
+
14
16
## Inputs
15
17
16
18
### `token` (string, required)
@@ -87,14 +89,16 @@ A string representing the HTTPS URL of the newly-forked repository.
If you are automating the creation of forks on behalf of a GitHub organization with many users, you may wish to leverage the optional `checkUser`, `promoteUser`, and `licenseAllowlist` params:
> 💡 **Tip:** Please use [node.js](https://nodejs.org/en/download/releases/) v17.x or later, as well as [TypeScript](https://www.npmjs.com/package/typescript) v4.x or later.
@@ -175,7 +181,7 @@ Then run [ncc](https://github.com/zeit/ncc) and push the results:
175
181
npm run package
176
182
git add dist
177
183
git commit -a -m "prod dependencies"
178
-
git push origin releases/v0.0.5
184
+
git push origin releases/v0.0.6
179
185
```
180
186
181
187
> 💡 **Tip:** We recommend using the `--license` option for `ncc`, which will create a license file for all of the production node modules used in your project.
0 commit comments