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: CONTRIBUTING.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -56,6 +56,6 @@ Only one version number is bumped at a time, the highest version change trumps t
56
56
Besides publishing a new version to npm, semantic-release also creates a git tag and release
57
57
on GitHub, generates changelogs from the commit messages and puts them into the release notes.
58
58
59
-
Before the publish it runs the `npm run build` script which creates a `pkg/` folder with distributions for browsers, node and Typescript definitions. The contents of the `pkg/` folder are published to the npm registry.
59
+
Before the publish it runs the `npm run build` script which creates a `pkg/` folder with distributions for browsers, node and TypeScript definitions. The contents of the `pkg/` folder are published to the npm registry.
60
60
61
61
If the pull request looks good but does not follow the commit conventions, use the <kbd>Squash & merge</kbd> button.
1. The name of the cursor variable must be `$cursor`
67
67
2. You must include a valid `pageInfo` object in the paginated resource (see [Pagination Direction](#pagination-direction) for more info on what is considered valid)
68
68
69
69
## `octokit.graphql.paginate()`
70
70
71
-
The `paginateGraphql` plugin adds a new `octokit.graphql.paginate()` method which accepts a query with a single `$cursor` variable that is used to paginate.
71
+
The `paginateGraphQL` plugin adds a new `octokit.graphql.paginate()` method which accepts a query with a single `$cursor` variable that is used to paginate.
72
72
73
73
The query gets passed over to the `octokit.graphql()`-function. The response is then scanned for the required `pageInfo`-object. If `hasNextPage` is `true`, it will automatically use the `endCursor` to execute the next query until `hasNextPage` is `false`.
74
74
75
-
While iterating, it ongoingly merges all `nodes` and/or `edges` of all responses and returns a combined response in the end.
75
+
While iterating, it continually merges all `nodes` and/or `edges` of all responses and returns a combined response in the end.
76
76
77
77
> **Warning**
78
78
> Please note that this plugin only supports pagination of a single resource - so you can **not** execute queries with parallel or nested pagination. You can find more details in [the chapter below](#unsupported-nested-pagination).
0 commit comments