privacyguides/i18n
1
0
Fork 0
mirror of https://github.com/privacyguides/i18n.git synced 2025-06-19 01:04:21 +00:00
Code Activity

New Crowdin translations by GitHub Action

Browse Source
This commit is contained in:
Crowdin Bot
2024-08-02 14:32:54 +00:00
parent 1256df84bb
commit c9f5133fcf
29 changed files with 435 additions and 261 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
i18n/ar/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/bn-IN/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/bn/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/cs/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/de/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/el/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/eo/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/es/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/fa/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/fr/meta/commit-messages.md
View File

@ -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. 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 ## 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 : 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/he/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/hi/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/hu/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/id/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/it/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/ja/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/ko/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/ku-IQ/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/nl/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/pl/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/pt-BR/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/pt/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/ru/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/sv/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/tr/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/uk/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/vi/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/zh-Hant/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets

24
i18n/zh/meta/commit-messages.md
View File

@ -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. 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 ## 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: 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 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 ## Development-related types
These commit types are typically used for changes that won't be visible to the general audience. 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`: 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 ```text
@ -64,7 +70,7 @@ We use `ci:` for commits related to GitHub Actions, DevContainers, or other auto
ci: Update Netlify config (#0000) 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 ```text
refactor: Move docs/assets to theme/assets refactor: Move docs/assets to theme/assets