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: .github/CONTRIBUTING.md
+7-3
Original file line number
Diff line number
Diff line change
@@ -82,7 +82,7 @@ ensure your pull request matches the style guides, run `npm run prettier`.
82
82
83
83
## Merge Process
84
84
85
-
Once a pull request has been approved by 2 reviewers from [`@graphql/graphql-js-reviewers`](https://github.com/orgs/graphql/teams/graphql-js-reviewers) team, we must wait 2 weeks before merging the pull request, this allows for other reviewers to give feedback without rushing any merges. Pull request can be merged by a member of the [`@graphql/graphql-js-reviewers`](https://github.com/orgs/graphql/teams/graphql-js-reviewers-write) team.
85
+
Once a pull request has been approved by 2 reviewers from [`@graphql/graphql-js-reviewers`](https://github.com/orgs/graphql/teams/graphql-js-reviewers) team, it may be merged by any member of the [`@graphql/graphql-js-reviewers`](https://github.com/orgs/graphql/teams/graphql-js-reviewers-write) team. For more complex pull requests, a larger cohort of reviewers is suggested. Any reviewer may request that the topic be brought for more in depth discussion at GraphQL JS Working Group meeting, where decisions will be made by consensus. A PR that has been merged without discussion at a GraphQL JS Working Group meeting may be reverted if a more in depth discussion is later requested.
86
86
87
87
## Release on NPM
88
88
@@ -93,18 +93,22 @@ then use `npm version patch|minor|major` in order to increment the version in
93
93
package.json and tag and commit a release. Then `git push && git push --tags`
94
94
to sync this change with source control. Then `npm publish npmDist` to actually
95
95
publish the release to NPM.
96
-
Once published, add [release notes](https://github.com/graphql/graphql-js/tags).
96
+
Once published, add [release notes](https://github.com/graphql/graphql-js/releases).
97
97
Use [semver](https://semver.org/) to determine which version part to increment.
98
98
99
99
Example for a patch release:
100
100
101
101
```sh
102
+
npm ci
102
103
npm test
103
104
npm version patch
104
105
git push --follow-tags
105
-
npm publish npmDist
106
+
cd npmDist && npm publish
107
+
npm run changelog
106
108
```
107
109
110
+
Then upload the changelog to [https://github.com/graphql/graphql-js/releases](https://github.com/graphql/graphql-js/releases).
111
+
108
112
## License
109
113
110
114
By contributing to graphql-js, you agree that your contributions will be
0 commit comments