chore: ignore SSL certificate error with conventionalcommits.org

This commit is contained in:
Daniel Roe 2024-04-19 17:31:46 +03:00
parent 506765e086
commit 9ba1ebe984
No known key found for this signature in database
GPG Key ID: CBC814C393D93268
4 changed files with 5 additions and 3 deletions

View File

@ -11,7 +11,7 @@ Before creating the pull request, please make sure you do the following:
- Check that there isn't already a PR that solves the problem the same way. If you find a duplicate, please help us reviewing it. - Check that there isn't already a PR that solves the problem the same way. If you find a duplicate, please help us reviewing it.
- Read the contribution docs at https://nuxt.com/docs/community/contribution - Read the contribution docs at https://nuxt.com/docs/community/contribution
- Ensure that PR title follows conventional commits (https://conventionalcommits.org) - Ensure that PR title follows conventional commits (https://www.conventionalcommits.org)
- Update the corresponding documentation if needed. - Update the corresponding documentation if needed.
- Include relevant tests that fail without this PR but pass with it. - Include relevant tests that fail without this PR but pass with it.

View File

@ -76,7 +76,7 @@ Before publishing your module to npm, makes sure you have an [npmjs.com](https:/
While you can publish your module by bumping its version and using the `npm publish` command, the module starter comes with a release script that helps you make sure you publish a working version of your module to npm and more. While you can publish your module by bumping its version and using the `npm publish` command, the module starter comes with a release script that helps you make sure you publish a working version of your module to npm and more.
To use the release script, first, commit all your changes (we recommend you follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0) to also take advantage of automatic version bump and changelog update), then run the release script with `npm run release`. To use the release script, first, commit all your changes (we recommend you follow [Conventional Commits](https://www.conventionalcommits.org) to also take advantage of automatic version bump and changelog update), then run the release script with `npm run release`.
When running the release script, the following will happen: When running the release script, the following will happen:

View File

@ -135,7 +135,7 @@ You can also run `pnpm lint:docs:fix` to highlight and resolve any lint issues.
### Open a PR ### Open a PR
Please make sure your PR title adheres to the [conventional commits](https://www.conventionalcommits.org/en/v1.0.0) guidelines. Please make sure your PR title adheres to the [conventional commits](https://www.conventionalcommits.org) guidelines.
```bash [Example of PR title] ```bash [Example of PR title]
docs: update the section about the nuxt.config.ts file docs: update the section about the nuxt.config.ts file

View File

@ -11,6 +11,8 @@ exclude = [
"https://twitter.nuxt.dev/", "https://twitter.nuxt.dev/",
"https://github.com/nuxt/translations/discussions/4", "https://github.com/nuxt/translations/discussions/4",
"https://stackoverflow.com/help/minimal-reproducible-example", "https://stackoverflow.com/help/minimal-reproducible-example",
# TODO: remove when their SSL certificate is valid again
"https://www.conventionalcommits.org",
# single-quotes are required for regexp # single-quotes are required for regexp
'(https?:\/\/github\.com\/)(.*\/)(generate)', '(https?:\/\/github\.com\/)(.*\/)(generate)',
] ]