From c9f5133fcfd29e1442ae9d5c3dfd50697e9c8d49 Mon Sep 17 00:00:00 2001 From: Crowdin Bot Date: Fri, 2 Aug 2024 14:32:54 +0000 Subject: [PATCH] New Crowdin translations by GitHub Action --- i18n/ar/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/bn-IN/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/bn/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/cs/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/de/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/el/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/eo/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/es/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/fa/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/fr/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/he/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/hi/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/hu/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/id/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/it/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/ja/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/ko/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/ku-IQ/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/nl/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/pl/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/pt-BR/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/pt/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/ru/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/sv/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/tr/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/uk/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/vi/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/zh-Hant/meta/commit-messages.md | 24 +++++++++++++++--------- i18n/zh/meta/commit-messages.md | 24 +++++++++++++++--------- 29 files changed, 435 insertions(+), 261 deletions(-) diff --git a/i18n/ar/meta/commit-messages.md b/i18n/ar/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/ar/meta/commit-messages.md +++ b/i18n/ar/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/bn-IN/meta/commit-messages.md b/i18n/bn-IN/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/bn-IN/meta/commit-messages.md +++ b/i18n/bn-IN/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/bn/meta/commit-messages.md b/i18n/bn/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/bn/meta/commit-messages.md +++ b/i18n/bn/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/cs/meta/commit-messages.md b/i18n/cs/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/cs/meta/commit-messages.md +++ b/i18n/cs/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/de/meta/commit-messages.md b/i18n/de/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/de/meta/commit-messages.md +++ b/i18n/de/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/el/meta/commit-messages.md b/i18n/el/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/el/meta/commit-messages.md +++ b/i18n/el/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/eo/meta/commit-messages.md b/i18n/eo/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/eo/meta/commit-messages.md +++ b/i18n/eo/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/es/meta/commit-messages.md b/i18n/es/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/es/meta/commit-messages.md +++ b/i18n/es/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/fa/meta/commit-messages.md b/i18n/fa/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/fa/meta/commit-messages.md +++ b/i18n/fa/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/fr/meta/commit-messages.md b/i18n/fr/meta/commit-messages.md index 8cf297ca..d18b2d98 100644 --- a/i18n/fr/meta/commit-messages.md +++ b/i18n/fr/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Message de commit avec correction - -Nous utilisons `fix` pour des choses simples comme les fautes d'orthographe ou les bugs liés au site. Ces choses ont généralement le label `correction` ou `bug` sur GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Fonctionnalité/amélioration Pour les nouvelles fonctionnalités ou les améliorations du site, par exemple les choses qui ont le label `enhancements` sur GitHub, il peut être approprié de les signifier avec : @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/he/meta/commit-messages.md b/i18n/he/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/he/meta/commit-messages.md +++ b/i18n/he/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/hi/meta/commit-messages.md b/i18n/hi/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/hi/meta/commit-messages.md +++ b/i18n/hi/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/hu/meta/commit-messages.md b/i18n/hu/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/hu/meta/commit-messages.md +++ b/i18n/hu/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/id/meta/commit-messages.md b/i18n/id/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/id/meta/commit-messages.md +++ b/i18n/id/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/it/meta/commit-messages.md b/i18n/it/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/it/meta/commit-messages.md +++ b/i18n/it/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/ja/meta/commit-messages.md b/i18n/ja/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/ja/meta/commit-messages.md +++ b/i18n/ja/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/ko/meta/commit-messages.md b/i18n/ko/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/ko/meta/commit-messages.md +++ b/i18n/ko/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/ku-IQ/meta/commit-messages.md b/i18n/ku-IQ/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/ku-IQ/meta/commit-messages.md +++ b/i18n/ku-IQ/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/nl/meta/commit-messages.md b/i18n/nl/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/nl/meta/commit-messages.md +++ b/i18n/nl/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/pl/meta/commit-messages.md b/i18n/pl/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/pl/meta/commit-messages.md +++ b/i18n/pl/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/pt-BR/meta/commit-messages.md b/i18n/pt-BR/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/pt-BR/meta/commit-messages.md +++ b/i18n/pt-BR/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/pt/meta/commit-messages.md b/i18n/pt/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/pt/meta/commit-messages.md +++ b/i18n/pt/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/ru/meta/commit-messages.md b/i18n/ru/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/ru/meta/commit-messages.md +++ b/i18n/ru/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/sv/meta/commit-messages.md b/i18n/sv/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/sv/meta/commit-messages.md +++ b/i18n/sv/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/tr/meta/commit-messages.md b/i18n/tr/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/tr/meta/commit-messages.md +++ b/i18n/tr/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/uk/meta/commit-messages.md b/i18n/uk/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/uk/meta/commit-messages.md +++ b/i18n/uk/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/vi/meta/commit-messages.md b/i18n/vi/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/vi/meta/commit-messages.md +++ b/i18n/vi/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/zh-Hant/meta/commit-messages.md b/i18n/zh-Hant/meta/commit-messages.md index ccb86eb4..7ef8da62 100644 --- a/i18n/zh-Hant/meta/commit-messages.md +++ b/i18n/zh-Hant/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets diff --git a/i18n/zh/meta/commit-messages.md b/i18n/zh/meta/commit-messages.md index 272dfa47..9b3c1ada 100644 --- a/i18n/zh/meta/commit-messages.md +++ b/i18n/zh/meta/commit-messages.md @@ -24,14 +24,6 @@ Foobar was removed due to it having numerious security issues and being unmainta You can actually add a `!` to _any_ of the types on this page to denote particularly large changes, but this is generally where it will be most appropriate. -## Commit message with correction - -We use `fix` for simple things like spelling mistakes or site related bugs. These things will usually have the `correction` or `bug` label on GitHub. - -```text -fix: Correct spelling on XYZ page (#0000) -``` - ## Feature/enhancement For new features or enhancements to the site, e.g. things that have the `enhancements` label on GitHub, it may be appropriate to signify these with: @@ -42,10 +34,24 @@ feat: Add blah blah (#0000) This change adds the forum topics to the main page ``` +## Minor changes + +Small changes that **don't affect the meaning** of the article, e.g. correcting a typo, fixing grammar, changing formatting/whitespace, CSS updates, etc. + +```text +style: Typo correction in VPN overview +``` + ## Development-related types These commit types are typically used for changes that won't be visible to the general audience. +We use `fix:` for changes that fix site related bugs. These things will usually have the `bug` label on GitHub. + +```text +fix: Remove broken Invidious embeds (#0000) +``` + We use `docs:` to denote changes to the developer documentation for this website, including (but not limited to) for example the README file, or most pages in `/docs/about` or `/docs/meta`: ```text @@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto ci: Update Netlify config (#0000) ``` -We use `refactor:` for changes which neither fix a bug nor add a feature. +We use `refactor:` for changes which neither fix a bug nor add a feature, e.g. rearranging files, navigation order, etc. ```text refactor: Move docs/assets to theme/assets