From 9ba1ebe984e135963eaeab7a819cc6ddca166bf4 Mon Sep 17 00:00:00 2001 From: Daniel Roe Date: Fri, 19 Apr 2024 17:31:46 +0300 Subject: [PATCH] chore: ignore SSL certificate error with `conventionalcommits.org` --- .github/PULL_REQUEST_TEMPLATE.md | 2 +- docs/2.guide/3.going-further/3.modules.md | 2 +- docs/5.community/5.framework-contribution.md | 2 +- lychee.toml | 2 ++ 4 files changed, 5 insertions(+), 3 deletions(-) diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index 8cba9c0e73..2618070610 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -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. - 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. - Include relevant tests that fail without this PR but pass with it. diff --git a/docs/2.guide/3.going-further/3.modules.md b/docs/2.guide/3.going-further/3.modules.md index 3eb0d0d424..8c354e5e21 100644 --- a/docs/2.guide/3.going-further/3.modules.md +++ b/docs/2.guide/3.going-further/3.modules.md @@ -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. -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: diff --git a/docs/5.community/5.framework-contribution.md b/docs/5.community/5.framework-contribution.md index 8dc6104142..2f70b77f98 100644 --- a/docs/5.community/5.framework-contribution.md +++ b/docs/5.community/5.framework-contribution.md @@ -135,7 +135,7 @@ You can also run `pnpm lint:docs:fix` to highlight and resolve any lint issues. ### 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] docs: update the section about the nuxt.config.ts file diff --git a/lychee.toml b/lychee.toml index 697f7aab92..b7cdde5945 100644 --- a/lychee.toml +++ b/lychee.toml @@ -11,6 +11,8 @@ exclude = [ "https://twitter.nuxt.dev/", "https://github.com/nuxt/translations/discussions/4", "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 '(https?:\/\/github\.com\/)(.*\/)(generate)', ]