-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' into perf/router-view-rerenders
- Loading branch information
Showing
248 changed files
with
16,314 additions
and
7,833 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -126,7 +126,7 @@ If you want to start translating the docs in a _new_ language: | |
1. Create the corresponding `<lang>` sub-folder for your translation. | ||
2. Modify the i18n configuration in the `.vitepress` sub-folder. | ||
3. Translate the docs and run the doc site to self-test locally. | ||
4. Create a checkpoint for your language by running `pnpm run docs:translation-status <lang> [<commit>]`. A checkpoint is the hash and date of the latest commit when you do the translation. The checkpoint information is stored in the status file `packages/docs/.vitepress/translation-status.json`. _It's crucial for long-term maintenance since all the further translation sync-ups are based on their previous checkpoints._ Usually, you can skip the commit argument because the default value is `main`. | ||
4. Create a checkpoint for your language by running `pnpm run docs:translation:update <lang> [<commit>]`. A checkpoint is the hash and date of the latest commit when you do the translation. The checkpoint information is stored in the status file `packages/docs/.vitepress/translation-status.json`. _It's crucial for long-term maintenance since all the further translation sync-ups are based on their previous checkpoints._ Usually, you can skip the commit argument because the default value is `main`. | ||
5. Commit all the changes and create a pull request to our GitHub repo. | ||
|
||
We will have a paragraph at the top of each translation page that shows the translation status. That way, users can quickly determine if the translation is up-to-date or lags behind the English version. | ||
|
@@ -135,9 +135,9 @@ Speaking of the up-to-date translation, we also need good long-term maintenance | |
|
||
1. See what translation you need to sync up with the original docs. There are two popular ways: | ||
1. Via the [GitHub Compare](https://github.com/vuejs/router/compare/) page, only see the changes in `packages/docs/*` from the checkpoint hash to `main` branch. You can find the checkpoint hash for your language via the translation status file `packages/docs/.vitepress/translation-status.json`. The compare page can be directly opened with the hash as part of the URL, e.g. https://github.com/vuejs/router/compare/e008551...main | ||
2. Via a local command: `pnpm run docs:compare-to-translate <lang> [<commit>]`. | ||
2. Via a local command: `pnpm run docs:translation:compare <lang> [<commit>]`. | ||
2. Create your own branch and start the translation update, following the previous comparison. | ||
3. Create a checkpoint for your language by running `pnpm run docs:translation-status <lang> [<commit>]`. | ||
3. Create a checkpoint for your language by running `pnpm run docs:translation:update <lang> [<commit>]`. | ||
4. Commit all the changes and create a pull request to our GitHub repo. | ||
|
||
<!-- TODO: add an example once we have got one --> | ||
|
@@ -149,18 +149,18 @@ You can also host the translation on your own. To create one, fork our GitHub re | |
- Ensure you maintain the _checkpoint_ properly. Also, ensure the _translation status_ is well-displayed on the top of each translation page. | ||
- Utilize the diff result between the latest official repository and your own checkpoint to guide your translation. | ||
|
||
Tip: you can add the official repo as a remote to your forked repo. This way, you can still run `pnpm run docs:translation-status <lang> [<commit>]` and `npm run docs:compare-to-translate <lang> [<commit>]` to get the checkpoint and diff result: | ||
Tip: you can add the official repo as a remote to your forked repo. This way, you can still run `pnpm run docs:translation:update <lang> [<commit>]` and `npm run docs:translation:compare <lang> [<commit>]` to get the checkpoint and diff result: | ||
|
||
```bash | ||
# prepare the upstream remote | ||
git remote add upstream [email protected]:vuejs/router.git | ||
git fetch upstream main | ||
|
||
# set the checkpoint | ||
pnpm run docs:translation-status <lang> upstream/main | ||
pnpm run docs:translation:update <lang> upstream/main | ||
|
||
# get the diff result | ||
pnpm run docs:compare-to-translate <lang> upstream/main | ||
pnpm run docs:translation:compare <lang> upstream/main | ||
``` | ||
|
||
<!-- TODO: add an example once we have got one --> | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
name: Publish Any Commit | ||
|
||
on: | ||
pull_request: | ||
branches: main | ||
paths-ignore: | ||
- 'packages/docs/**' | ||
- 'packages/playground/**' | ||
|
||
push: | ||
branches: | ||
- '**' | ||
tags: | ||
- '!**' | ||
paths-ignore: | ||
- 'packages/docs/**' | ||
- 'packages/playground/**' | ||
|
||
jobs: | ||
build: | ||
runs-on: ubuntu-latest | ||
|
||
steps: | ||
- name: Checkout code | ||
uses: actions/checkout@v4 | ||
with: | ||
fetch-depth: 0 | ||
- uses: pnpm/action-setup@v4 | ||
- uses: actions/setup-node@v4 | ||
with: | ||
node-version: lts/* | ||
cache: pnpm | ||
|
||
- name: Install | ||
run: pnpm install --frozen-lockfile | ||
|
||
- name: Build | ||
run: pnpm -C packages/router build | ||
|
||
- name: Build DTS | ||
run: pnpm -C packages/router build:dts | ||
|
||
- name: Release | ||
run: pnpm dlx pkg-pr-new publish --compact --pnpm './packages/*' |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
# Reporting a Vulnerability | ||
|
||
To report a vulnerability, please email [email protected]. | ||
|
||
While the discovery of new vulnerabilities is rare, we also recommend always using the latest versions of Vue and its official companion libraries to ensure your application remains as secure as possible. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
coverage: | ||
status: | ||
patch: off | ||
project: | ||
default: | ||
threshold: 2% |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.