summarize scripts

.github/workflows/tests.yml

@@ -21,7 +21,7 @@ jobs:
       - name: Set up
         uses: ./.github/actions/setup
       - name: Run unit tests
-        run: ./execute_tests.bash
+        run: ./scripts/execute_tests.bash
 
   example:
     runs-on: ubuntu-22.04
@@ -33,7 +33,7 @@ jobs:
       - name: Set up
         uses: ./.github/actions/setup
       - name: Validate example
-        run: ./validate_example.bash
+        run: ./scripts/validate_example.bash
 
   style-check:
     runs-on: ubuntu-22.04
@@ -45,7 +45,7 @@ jobs:
       - name: Set up
         uses: ./.github/actions/setup
       - name: Run formatters and linters
-        run: ./style_check.bash
+        run: ./scripts/style_check.bash
       - name: Fail if some files are changed
         run: |
           if ! git diff --exit-code; then

README.md

@@ -40,9 +40,9 @@ In order to specify how to validate the error message, a struct `matcher` is ava
 
 ### How to test
 
-Execute [`execute_tests.bash`](execute_tests.bash) after installing [`bazelisk`](https://github.com/bazelbuild/bazelisk). It executes `bazelisk test` and `bazelisk build` commands under the hood.
+Execute [`scripts/execute_tests.bash`](scripts/execute_tests.bash) after installing [`bazelisk`](https://github.com/bazelbuild/bazelisk). It executes `bazelisk test` and `bazelisk build` commands under the hood.
 
-When writing tests, in principle, use `tags = ["manual"]` if a test case target must fail with `bazelisk test`. In such a test case, confirm its failure in [`execute_tests.bash`](execute_tests.bash) one by one.
+When writing tests, in principle, use `tags = ["manual"]` if a test case target must fail with `bazelisk test`. In such a test case, confirm its failure in [`scripts/execute_tests.bash`](scripts/execute_tests.bash) one by one.
 
 ## CI