CONTRIBUTING: cleare separate section for maintainers only about create-octokit-project.js

[gr2m]

good questions, I should have been more clear. It was a question by someone who wanted to send a pull request to @octokit/rest documentation but didn't understand the commit conventions. If it was clear that these are only relevant to maintainers then the problem would not have occured.

I think I would add a new header ## Maintainers only here:

create-octokit-project.js/lib/create-contributing.js

Lines 62 to 77 in 51f5a55

	## Merging the Pull Request & releasing a new version
	Releases are automated using [semantic-release](https://github.com/semantic-release/semantic-release).
	The following commit message conventions determine which version is released:
	1. \`fix: ...\` or \`fix(scope name): ...\` prefix in subject: bumps fix version, e.g. \`1.2.3\` → \`1.2.4\`
	2. \`feat: ...\` or \`feat(scope name): ...\` prefix in subject: bumps feature version, e.g. \`1.2.3\` → \`1.3.0\`
	3. \`BREAKING CHANGE:\` in body: bumps breaking version, e.g. \`1.2.3\` → \`2.0.0\`
	Only one version number is bumped at a time, the highest version change trumps the others.
	Besides publishing a new version to npm, semantic-release also creates a git tag and release
	on GitHub, generates changelogs from the commit messages and puts them into the release notes.
	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.
	If the pull request looks good but does not follow the commit conventions, use the <kbd>Squash & merge</kbd> button.

and then make the current heading level 3: ### Merging the Pull Request & releasing a new version. That should be clear enough?

[gr2m]

I'd PR it in this case, because this is such a meta repository

[oscard0m]

What was the issue with this? (any confusion with contributors so it is needed to improve this description?), also, what do you have in mind? Just highlighting a disclaimer for that section saying is for maintainers only?

[oscard0m]

good questions, I should have been more clear. It was a question by someone who wanted to send a pull request to @octokit/rest documentation but didn't understand the commit conventions. If it was clear that these are only relevant to maintainers then the problem would not have occured.

I think I would add a new header ## Maintainers only here:

create-octokit-project.js/lib/create-contributing.js

Lines 62 to 77 in 51f5a55

	## Merging the Pull Request & releasing a new version
	Releases are automated using [semantic-release](https://github.com/semantic-release/semantic-release).
	The following commit message conventions determine which version is released:
	1. \`fix: ...\` or \`fix(scope name): ...\` prefix in subject: bumps fix version, e.g. \`1.2.3\` → \`1.2.4\`
	2. \`feat: ...\` or \`feat(scope name): ...\` prefix in subject: bumps feature version, e.g. \`1.2.3\` → \`1.3.0\`
	3. \`BREAKING CHANGE:\` in body: bumps breaking version, e.g. \`1.2.3\` → \`2.0.0\`
	Only one version number is bumped at a time, the highest version change trumps the others.
	Besides publishing a new version to npm, semantic-release also creates a git tag and release
	on GitHub, generates changelogs from the commit messages and puts them into the release notes.
	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.
	If the pull request looks good but does not follow the commit conventions, use the <kbd>Squash & merge</kbd> button.

and then make the current heading level 3: ### Merging the Pull Request & releasing a new version. That should be clear enough?

Yep. I guess this a goodfirstissue, should we leave it? Or just PR it?

[github-actions]

🎉 This issue has been resolved in version 1.9.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀