From 46f003afee2b913ad07dc00c27eeb8242067a96b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E3=83=9E=E3=83=AB=E3=82=B3=E3=83=A1?= Date: Mon, 7 Oct 2024 16:35:56 +0900 Subject: [PATCH 1/5] docs: apply alert style correctly at warning message --- README.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index 3fbca53..4f03a00 100644 --- a/README.md +++ b/README.md @@ -119,14 +119,14 @@ So, what are you waiting for? Go ahead and start customizing your action! npm run all ``` - > [!WARNING] - > - > This step is important! It will run [`ncc`](https://github.com/vercel/ncc) - > to build the final JavaScript action code with all dependencies included. - > If you do not run this step, your action will not work correctly when it is - > used in a workflow. This step also includes the `--license` option for - > `ncc`, which will create a license file for all of the production node - > modules used in your project. +> [!WARNING] +> +> This step is important! It will run [`ncc`](https://github.com/vercel/ncc) +> to build the final JavaScript action code with all dependencies included. +> If you do not run this step, your action will not work correctly when it is +> used in a workflow. This step also includes the `--license` option for +> `ncc`, which will create a license file for all of the production node +> modules used in your project. 1. Commit your changes From 56bfdb077edda1804220fa4649a6148c0b69b36d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E3=83=9E=E3=83=AB=E3=82=B3=E3=83=A1?= Date: Mon, 7 Oct 2024 21:23:59 +0900 Subject: [PATCH 2/5] docs: fix list number --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 4f03a00..3fcd65f 100644 --- a/README.md +++ b/README.md @@ -128,21 +128,21 @@ So, what are you waiting for? Go ahead and start customizing your action! > `ncc`, which will create a license file for all of the production node > modules used in your project. -1. Commit your changes +5. Commit your changes ```bash git add . git commit -m "My first action is ready!" ``` -1. Push them to your repository +6. Push them to your repository ```bash git push -u origin releases/v1 ``` -1. Create a pull request and get feedback on your action -1. Merge the pull request into the `main` branch +7. Create a pull request and get feedback on your action +8. Merge the pull request into the `main` branch Your action is now published! :rocket: From 558c75a530da8c468877022f475c41d48f67ba00 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E3=83=9E=E3=83=AB=E3=82=B3=E3=83=A1?= Date: Mon, 7 Oct 2024 21:32:02 +0900 Subject: [PATCH 3/5] chore: lint README.md --- README.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 3fcd65f..11c55dc 100644 --- a/README.md +++ b/README.md @@ -121,12 +121,12 @@ So, what are you waiting for? Go ahead and start customizing your action! > [!WARNING] > -> This step is important! It will run [`ncc`](https://github.com/vercel/ncc) -> to build the final JavaScript action code with all dependencies included. -> If you do not run this step, your action will not work correctly when it is -> used in a workflow. This step also includes the `--license` option for -> `ncc`, which will create a license file for all of the production node -> modules used in your project. +> This step is important! It will run [`ncc`](https://github.com/vercel/ncc) to +> build the final JavaScript action code with all dependencies included. If you +> do not run this step, your action will not work correctly when it is used in a +> workflow. This step also includes the `--license` option for `ncc`, which will +> create a license file for all of the production node modules used in your +> project. 5. Commit your changes From 936ae24c2b497df7319405825c8020f3499615b2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E3=83=9E=E3=83=AB=E3=82=B3=E3=83=A1?= Date: Sat, 12 Oct 2024 17:23:19 +0900 Subject: [PATCH 4/5] docs: change list numbering --- README.md | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index 11c55dc..5ce6f4a 100644 --- a/README.md +++ b/README.md @@ -121,28 +121,28 @@ So, what are you waiting for? Go ahead and start customizing your action! > [!WARNING] > -> This step is important! It will run [`ncc`](https://github.com/vercel/ncc) to -> build the final JavaScript action code with all dependencies included. If you -> do not run this step, your action will not work correctly when it is used in a -> workflow. This step also includes the `--license` option for `ncc`, which will -> create a license file for all of the production node modules used in your -> project. + > This step is important! It will run [`ncc`](https://github.com/vercel/ncc) + > to build the final JavaScript action code with all dependencies included. + > If you do not run this step, your action will not work correctly when it is + > used in a workflow. This step also includes the `--license` option for + > `ncc`, which will create a license file for all of the production node + > modules used in your project. -5. Commit your changes +1. Commit your changes ```bash git add . git commit -m "My first action is ready!" ``` -6. Push them to your repository +1. Push them to your repository ```bash git push -u origin releases/v1 ``` -7. Create a pull request and get feedback on your action -8. Merge the pull request into the `main` branch +1. Create a pull request and get feedback on your action +1. Merge the pull request into the `main` branch Your action is now published! :rocket: From 023fbfd7d2fddeb9252e4650f1d1138a96bfbd48 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E3=83=9E=E3=83=AB=E3=82=B3=E3=83=A1?= Date: Sat, 12 Oct 2024 18:11:11 +0900 Subject: [PATCH 5/5] docs: remove warning alert --- README.md | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index 5ce6f4a..8ddd03c 100644 --- a/README.md +++ b/README.md @@ -119,14 +119,12 @@ So, what are you waiting for? Go ahead and start customizing your action! npm run all ``` -> [!WARNING] -> - > This step is important! It will run [`ncc`](https://github.com/vercel/ncc) - > to build the final JavaScript action code with all dependencies included. - > If you do not run this step, your action will not work correctly when it is - > used in a workflow. This step also includes the `--license` option for - > `ncc`, which will create a license file for all of the production node - > modules used in your project. + > This step is important! It will run [`ncc`](https://github.com/vercel/ncc) + > to build the final JavaScript action code with all dependencies included. + > If you do not run this step, your action will not work correctly when it is + > used in a workflow. This step also includes the `--license` option for + > `ncc`, which will create a license file for all of the production node + > modules used in your project. 1. Commit your changes