Change Python script arguments from hyphens to underscores (#483)

- --skip-build → --skip_build
- --skip-install → --skip_install
- --only-check-file-extensions → --only_check_file_extensions
- --sharding-instances → --sharding_instances

Author: seanlip

Backend-Type-Annotations.md

@@ -25,7 +25,7 @@ python -m scripts.run_mypy_checks --files path/file1.py path/file2.py
   This runs the type checks on the files specified, i.e., file1 and file2.
 
 **Note:**
-- [Helpful trick for faster runs]`python -m scripts.run_mypy_checks --skip-install` can be used to skip installation of third party libraries. Please use the `--skip-install` flag **only** when you already have all the third party libraries installed.
+- [Helpful trick for faster runs]`python -m scripts.run_mypy_checks --skip_install` can be used to skip installation of third party libraries. Please use the `--skip_install` flag **only** when you already have all the third party libraries installed.
 
 
 ## Adding type annotations

Backend-tests.md

@@ -182,15 +182,15 @@ python -m scripts.run_backend_tests --help
 
 Note that while the tests are running, you may see the word `ERROR` show up in the test logs. This does not necessarily mean that an error has occurred; it happens because some tests actually expect an error to be raised.
 
-If you want to speed up subsequent runs of the tests, use `--skip-install` like this:
+If you want to speed up subsequent runs of the tests, use `--skip_install` like this:
 
 ```console
-python -m scripts.run_backend_tests --skip-install
+python -m scripts.run_backend_tests --skip_install
 ```
 
 You can also combine this flag with the ones mentioned above. For example, you can use it with the `--test-targets` flag for even faster runs like this:
 ```console
-python -m scripts.run_backend_tests --test_targets=core.controllers.editor_test --skip-install
+python -m scripts.run_backend_tests --test_targets=core.controllers.editor_test --skip_install
 ```
 
 Note that this skips reinstalling the required libraries, so remember to run the tests without this flag every once in a while to keep them up to date.

Coding-style-guide.md

@@ -417,7 +417,7 @@ python -m scripts.linters.run_lint_checks --files file_1 file_2 ... file_n
 
 If you'd like to run the checks for a list of file-types, run the following command:
 ```bash
-python -m scripts.linters.run_lint_checks --only-check-file-extensions file_extension_type_1 file_extension_type_2 ... file_extension_type_n
+python -m scripts.linters.run_lint_checks --only_check_file_extensions file_extension_type_1 file_extension_type_2 ... file_extension_type_n
 ```
 
 ### Note for Sublime Text users

End-to-End-Tests.md

@@ -218,7 +218,7 @@ If you run all the E2E tests at once (i.e. if you don't specify a suite), the te
 
 Python:
 ```console
-python -m scripts.run_e2e_tests --sharding-instances=<number of shards>
+python -m scripts.run_e2e_tests --sharding_instances=<number of shards>
 ```
 
 You can disable sharding like this:

Frequently-Asked-Questions.md

@@ -37,7 +37,7 @@ python -m scripts.linters.run_lint_checks --path=path/to/the/file
 
 Let's say you want to run the linting tests on a specific file type. In the oppia directory, run the following command.
 
-python -m scripts.linters.run_lint_checks --only-check-file-extensions file_extension_type
+python -m scripts.linters.run_lint_checks --only_check_file_extensions file_extension_type
 
 ### How to test email functionality?
  Please refer to [Testing-email-functionality](https://github.com/oppia/oppia/wiki/Testing-email-functionality) for details.

Lint-Checks.md

@@ -62,13 +62,13 @@ We use linters to check our code for common errors or bad patterns. The Oppia li
 5. To lint a specific list of file extensions (separated by spaces):
 
    ```console
-   python -m scripts.linters.run_lint_checks --only-check-file-extensions {{extensions}}
+   python -m scripts.linters.run_lint_checks --only_check_file_extensions {{extensions}}
    ```
 
    For example, to lint Python and JavaScript files, you could run this:
 
    ```console
-   python -m scripts.linters.run_lint_checks --only-check-file-extensions py js
+   python -m scripts.linters.run_lint_checks --only_check_file_extensions py js
    ```
 
 ## Write lint checks

Tutorial-Learn-How-to-Fix-a-CI-Flake-waitFor-Statements.md

@@ -354,16 +354,16 @@ Here’s how:
 command: >
            VIDEO_RECORDING_IS_ENABLED=0;
            xvfb-run -a --server-args="-screen 0, 1285x1000x24"
-           python -m scripts.run_e2e_tests --skip-install
-           --skip-build --prod_env
+           python -m scripts.run_e2e_tests --skip_install
+           --skip_build --prod_env
 ```
 - You can adjust it to run only the relevant suite by adding the suitable flag, like so:
 ```yml
 command: >
            VIDEO_RECORDING_IS_ENABLED=0;
            xvfb-run -a --server-args="-screen 0, 1285x1000x24"
-           python -m scripts.run_e2e_tests --skip-install
-           --skip-build --suite=additionalEditorFeatures --prod_env
+           python -m scripts.run_e2e_tests --skip_install
+           --skip_build --suite=additionalEditorFeatures --prod_env
 ```
 - Now the workflow `step check_test_suites_to_run:
 uses: ./.github/workflows/check_test_suites_to_run.yml.`