Spelling

.github/workflows/codeql.yml

@@ -20,7 +20,7 @@ on:
   schedule:
     - cron: '32 22 * * 6'
 
-permissions:  # limit the permissions of the GITHIUB_TOKEN to reading repository contents
+permissions:  # limit the permissions of the GITHUB_TOKEN to reading repository contents
   contents: read
 
 jobs:

.github/workflows/generate_release_notes.yml

@@ -3,7 +3,7 @@ name: "[Release] Step 1: Generate release notes"
 on:
   workflow_dispatch:
 
-# limit the permissions of the GITHIUB_TOKEN to reading repository contents
+# limit the permissions of the GITHUB_TOKEN to reading repository contents
 # the subsequent pull request uses a token from the 'generate-token' step
 permissions:
   contents: read

.github/workflows/integration_tests_pointer.yml

@@ -6,7 +6,7 @@ on:
   repository_dispatch:
     types: [ integration-pointer]
 
-permissions:  # limit the permissions of the GITHIUB_TOKEN to reading repository contents
+permissions:  # limit the permissions of the GITHUB_TOKEN to reading repository contents
   contents: read
 
 jobs:

.github/workflows/macos_workflow.yml

@@ -8,7 +8,7 @@ on:
     branches:
       - '*'
 
-permissions:  # limit the permissions of the GITHIUB_TOKEN to reading repository contents
+permissions:  # limit the permissions of the GITHUB_TOKEN to reading repository contents
   contents: read
 
 jobs:

.github/workflows/release.yml

@@ -12,7 +12,7 @@ on:
     tags: v*
 
 # TODO: update workflow permissions to least privilege after auditing all the APIs used
-# permissions:  # limit the permissions of the GITHIUB_TOKEN to reading repository contents
+# permissions:  # limit the permissions of the GITHUB_TOKEN to reading repository contents
 #   contents: read
 
 jobs:

.github/workflows/release_flank_scripts.yml

@@ -8,7 +8,7 @@ on:
       - 'master'
 
 # TODO: update workflow permissions to least privilege after auditing all the APIs used
-# permissions:  # limit the permissions of the GITHIUB_TOKEN to reading repository contents
+# permissions:  # limit the permissions of the GITHUB_TOKEN to reading repository contents
 #   contents: read
 
 jobs:
@@ -25,7 +25,7 @@ jobs:
     - uses: actions/checkout@v4
     - uses: gradle/wrapper-validation-action@v3
 
-    - name: Gradle Upload to Github packages and Github release
+    - name: Gradle Upload to GitHub packages and GitHub release
       uses: gradle/[email protected]
       env:
         GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/release_flank_wrapper.yml

@@ -8,7 +8,7 @@ on:
       - 'master'
 
 # TODO: update workflow permissions to least privilege after auditing all the APIs used
-# permissions:  # limit the permissions of the GITHIUB_TOKEN to reading repository contents
+# permissions:  # limit the permissions of the GITHUB_TOKEN to reading repository contents
 #   contents: read
 
 jobs:
@@ -25,7 +25,7 @@ jobs:
     - uses: actions/checkout@v4
     - uses: gradle/wrapper-validation-action@v3
 
-    - name: Gradle Upload to Github packages and Github release
+    - name: Gradle Upload to GitHub packages and GitHub release
       uses: gradle/[email protected]
       env:
         GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/run_integration_tests.yml

@@ -6,7 +6,7 @@ on:
   workflow_dispatch:      # or manually
 
 # TODO: update workflow permissions to least privilege after auditing all the APIs used
-# permissions:  # limit the permissions of the GITHIUB_TOKEN to reading repository contents
+# permissions:  # limit the permissions of the GITHUB_TOKEN to reading repository contents
 #   contents: read
 
 jobs:

.github/workflows/tag_next_release.yml

@@ -6,7 +6,7 @@ on:
     types: [ closed ]
 
 # TODO: update workflow permissions to least privilege after auditing all the APIs used
-# permissions:  # limit the permissions of the GITHIUB_TOKEN to reading repository contents
+# permissions:  # limit the permissions of the GITHUB_TOKEN to reading repository contents
 #   contents: read
 
 jobs:

.github/workflows/ubuntu_workflow.yml

@@ -8,7 +8,7 @@ on:
     branches:
       - '*'
 
-permissions:  # limit the permissions of the GITHIUB_TOKEN to reading repository contents
+permissions:  # limit the permissions of the GITHUB_TOKEN to reading repository contents
   contents: read
 
 jobs:

.github/workflows/update_dependencies.yml

@@ -4,7 +4,7 @@ on:
   workflow_dispatch:
 
 # TODO: update workflow permissions to least privilege after auditing all the APIs used
-# permissions:  # limit the permissions of the GITHIUB_TOKEN to reading repository contents
+# permissions:  # limit the permissions of the GITHUB_TOKEN to reading repository contents
 #   contents: read
 
 jobs:
@@ -101,7 +101,7 @@ jobs:
           body: "Firebase Api update"
           labels: |
             automated pr
-            firease_api
+            firebase_api
           reviewers: adamvduke,jakeouellette,tonybaroneee
           draft: false
 

.github/workflows/update_dependencies_pointer.yml

@@ -6,7 +6,7 @@ on:
   repository_dispatch:
     types: [ dependencies-pointer ]
 
-permissions:  # limit the permissions of the GITHIUB_TOKEN to reading repository contents
+permissions:  # limit the permissions of the GITHUB_TOKEN to reading repository contents
   contents: read
 
 jobs:

.github/workflows/windows_workflow.yml

@@ -5,7 +5,7 @@ on:
     branches:
       - '*'
 
-permissions:  # limit the permissions of the GITHIUB_TOKEN to reading repository contents
+permissions:  # limit the permissions of the GITHUB_TOKEN to reading repository contents
   contents: read
 
 jobs:

README.md

@@ -7,4 +7,4 @@ Flank is YAML compatible with [the gcloud CLI](https://cloud.google.com/sdk/gclo
 ### Documentation is at [flank.github.io/flank](https://flank.github.io/flank/)
 
 
-### Github action documentation is at [repository](https://github.com/Flank/flank/blob/master/docs/flank-github-action/store_documentation.md)
+### GitHub action documentation is at [repository](https://github.com/Flank/flank/blob/master/docs/flank-github-action/store_documentation.md)

action.yml

@@ -1,5 +1,5 @@
 name: 'Flank'
-description: 'Run Flank from Github actions!'
+description: 'Run Flank from GitHub actions!'
 inputs:
   version: 
     description: 'Flank version to run'

check_version_updated/src/main/kotlin/com/github/flank/gradle/CheckVersionUpdated.kt

@@ -32,9 +32,9 @@ class CheckVersionUpdated : Plugin<Project> {
 
         val localResultsStream = execAndGetStdout("git", "diff", "origin/master", "HEAD", "--", "build.gradle.kts")
             .split("\n")
-        val commitedResultsStream = execAndGetStdout("git", "diff", "origin/master", "--", "build.gradle.kts")
+        val committedResultsStream = execAndGetStdout("git", "diff", "origin/master", "--", "build.gradle.kts")
             .split("\n")
-        return (commitedResultsStream + localResultsStream)
+        return (committedResultsStream + localResultsStream)
             .filter { it.startsWith("-version = ") || it.startsWith("+version = ") }
             .isNotEmpty()
     }

check_version_updated/src/main/kotlin/com/github/flank/gradle/CheckVersionUpdatedTask.kt

@@ -43,9 +43,9 @@ open class CheckVersionUpdatedTask : DefaultTask() {
     private fun Project.isVersionChangedInBuildGradle(): Boolean {
         val localResultsStream = execAndGetStdout("git", "diff", "origin/master", "HEAD", "--", "build.gradle.kts")
             .split("\n")
-        val commitedResultsStream = execAndGetStdout("git", "diff", "origin/master", "--", "build.gradle.kts")
+        val committedResultsStream = execAndGetStdout("git", "diff", "origin/master", "--", "build.gradle.kts")
             .split("\n")
-        return (commitedResultsStream + localResultsStream)
+        return (committedResultsStream + localResultsStream)
             .any { it.startsWith("-version = ") || it.startsWith("+version = ") }
     }
 

contributing.md

@@ -27,16 +27,16 @@ There is a [`Debug.kt`](https://github.com/Flank/flank/blob/master/test_runner/s
 
 Note: The breakpoints will only hit for the actual command being run. For example, for `firebase test android run`, the debugger will directly enter [`AndroidRunCommand`](https://github.com/Flank/flank/blob/master/test_runner/src/main/kotlin/ftl/cli/firebase/test/android/AndroidRunCommand.kt).
 
-The yml file being read is located [here](https://github.com/Flank/flank/blob/master/test_runner/flank.yml).
+The yml file being read is located at [test_runner/flank.yml](https://github.com/Flank/flank/blob/master/test_runner/flank.yml).
 
 Run `./gradlew check` to fix lint issues
 
 ## Adding new gcloud property common to iOS and Android
 
 - Add property to `GcloudYml` and update `keys` in config files
 - Update `IArgs` with new property
-- Update `AndroidArgs` to reference the propery and update `toString`
-- Update `IosArgs` to reference the propery and `toString`
+- Update `AndroidArgs` to reference the property and update `toString`
+- Update `IosArgs` to reference the property and `toString`
 - Add test to `IosArgsTest`
 - Add test to `IosRunCommandTest` and update `empty_params_parse_null` test
 - Add test to `AndroidArgsTest`

docs/bugs/872_error_when_parsing_Junit_raport_using_TeamCityCI.md

@@ -178,7 +178,7 @@ But when user back to old configuration, he can still reproduce problem.
 
 #### Issue reported to TeamCity https://youtrack.jetbrains.com/issue/TW-66753
 
-TeamCity team cannot reproduce the problem, thay asked about additional logs, but User could deliver them in next week (starting 13-07-2020), until that we must wait.
+TeamCity team cannot reproduce the problem, they asked about additional logs, but User could deliver them in next week (starting 13-07-2020), until that we must wait.
 
 
 

docs/bugs/891-rate-limit-exceeded.md

@@ -202,7 +202,7 @@ forEach(test matrix) {
 }
 ```
 
-## API calls usage comparision table
+## API calls usage comparison table
 Following table should compare API calls complexity.
 
 |         | execution status updates |
@@ -219,7 +219,7 @@ E - count of test executions in matrix scope
 ```
 
 ## Conclusions
-#### Gclud
+#### Gcloud
 Because of single matrix run gives only 1 request per 6 seconds
 
 #### Flank v20.05.2

docs/bugs/993_multiple_identical_lines_printing.md

@@ -21,4 +21,4 @@ It always executes on the same thread so it is not a concurrency issue
 
 - [X] on ```ExecutionStatusPrinter.kt``` -> ```MultiLinePrinter``` try to force add to output two same ExecutionStatus but no effect
 
-- [X] on ```GcTestMatrix.kt``` -> ```refresh()``` try to add testSpecyfication with same id but without effect
+- [X] on ```GcTestMatrix.kt``` -> ```refresh()``` try to add testSpecification with same id but without effect

docs/bugs/null_no_tests_found.md

@@ -80,7 +80,7 @@ gcloud:
   use-orchestrator: true
 ```
 
-## Reported flade config
+## Reported fladle config
 ```groovy
 fladle {
     serviceAccountCredentials = file("pathToCredentials")
@@ -120,4 +120,4 @@ fladle {
 * Create multi-module project which will provide many test apks and try to reproduce issue.
 * Ensure that our knowledge about issue in `What we know from report issue` is correct.
 * Based on: https://stackoverflow.com/questions/39241640/android-instrumented-test-no-tests-found try to make real multi dex app and try trun tests on it
-* Play with @BefeoreClass and @Before annotations (exception on @BeforeClass produce null without test cases on test-lab).
+* Play with @BeforeClass and @Before annotations (exception on @BeforeClass produce null without test cases on test-lab).

docs/building_updating_flank.md

@@ -1,5 +1,5 @@
 # Building and Updating Flank
-Ensure that all steps taken for contributing and building Flank have been followed, which are found [here](../README.md)
+Ensure that you have followed all steps for [contributing and building Flank](../README.md)
 
 ## Building an updated flank
 To build an updated version of flank from source simply run (This assumes you are in the root Flank directory)

docs/client_generation.md

@@ -14,7 +14,7 @@ Google API clients (`google-api-*-client`)
 - Low level
 - Auto generated
 - Made for JSON REST APIs
-- Older project - [maintence mode](https://github.com/GoogleCloudPlatform/google-cloud-ruby/issues/1604#issuecomment-316834237)
+- Older project - [maintenance mode](https://github.com/GoogleCloudPlatform/google-cloud-ruby/issues/1604#issuecomment-316834237)
 
 Google APIs toolkit (`googleapis/toolkit`)
 - Low level
@@ -36,7 +36,7 @@ Google Cloud libraries (`google-cloud-*`)
 - [google-api-go-client](https://github.com/google/google-api-go-client)
   - [google-api-go-generator](https://github.com/google/google-api-go-client/tree/master/google-api-go-generator)
 - [google-api-java-client](https://github.com/google/google-api-java-client)
-- [google-api-javascript-client](https://github.com/google/google-api-javascript-client) - not offically [marked as maintence,](https://github.com/google/google-api-javascript-client/issues/320) however no new updates since May 2017.
+- [google-api-javascript-client](https://github.com/google/google-api-javascript-client) - not officially [marked as maintenance,](https://github.com/google/google-api-javascript-client/issues/320) however no new updates since May 2017.
 - [google-api-dotnet-client](https://github.com/google/google-api-dotnet-client)
 - [google-api-objectivec-client](https://github.com/google/google-api-objectivec-client)
   - Deprecated. Replaced entirely by [google-api-objectivec-client-for-rest](https://github.com/google/google-api-objectivec-client-for-rest)

docs/dependencies_update_process.md

@@ -6,7 +6,7 @@ Process run commands and update files with defined versions in the provided file
 ### Modules
 0. [Gradle Versions Plugin](https://github.com/ben-manes/gradle-versions-plugin) which check dependencies version and generate report
 0. [Command](../flank-scripts/README.md#dependencies) in `flank-scripts` which update dependencies versions
-0. Github action job which runs dependencies check every Monday at 5 AM UTC or on-demand
+0. GitHub action job which runs dependencies check every Monday at 5 AM UTC or on-demand
 
 ## Usage
 
@@ -15,8 +15,8 @@ Process run commands and update files with defined versions in the provided file
 0. Build flank scripts using script `./flank-scripts/bash/buildFlankScripts.sh`
 0. Run `./flank-scripts/bash/flankScripts dependencies update`
 
-### Github action
-Run `Update dependencies` job using [Github action menu](https://github.com/Flank/flank/actions) by clicking `Run workflow` button
+### GitHub action
+Run `Update dependencies` job using [GitHub action menu](https://github.com/Flank/flank/actions) by clicking `Run workflow` button
 
 ## Merging to master
 

docs/feature/summary_output.md

@@ -67,7 +67,7 @@ Gcloud is using following API calls
 2. `self._client.projects_histories_executions_steps.List(request)`
 
 The first one is default, but if returns any `environment` without `environmentResult.outcome`, the second one will be used to obtain `steps`. 
-Both `environemnts` and `steps` can provide `outcome`. The difference between them is the `steps` returns `success` event if tests are `flaky`.
+Both `environments` and `steps` can provide `outcome`. The difference between them is the `steps` returns `success` event if tests are `flaky`.
 Currently, we don't know why `self._client.projects_histories_executions_environments.List(request)` may return empty `environmentResult.outcome`.
 
 In difference to gcloud flank uses 3 api call to obtain necessary data

docs/flank-github-action/flank_github_acton_sdd.md

@@ -1,26 +1,26 @@
-# Flank Github action
+# Flank GitHub action
 
-Add Github action which allows running Flank
+Add GitHub action which allows running Flank
 
 # References
 
-- [Github actions documentation](https://github.com/features/actions)
+- [GitHub actions documentation](https://github.com/features/actions)
 
 - [Creating a Docker container action](https://docs.github.com/en/actions/creating-actions/creating-a-docker-container-action)
 
 - [Creating a JavaScript action](https://docs.github.com/en/actions/creating-actions/creating-a-javascript-action)
 
 - [Creating a composite run steps action](https://docs.github.com/en/actions/creating-actions/creating-a-composite-run-steps-action)
 
-- [Github actions marketplace](https://github.com/marketplace?type=actions)
+- [GitHub actions marketplace](https://github.com/marketplace?type=actions)
 
 
 
 # Motivation
 
-Bitrise and Circle CI have steps in their CIs to run Flank. As Github is a widely used code repository and Github actions become more and more popular there should be also Github action that allows running Flank. 
+Bitrise and Circle CI have steps in their CIs to run Flank. As GitHub is a widely used code repository and GitHub actions become more and more popular there should be also GitHub action that allows running Flank. 
 
-After creating Github action, Flank could reach more users.
+After creating GitHub action, Flank could reach more users.
 
 # Goals
 
@@ -30,7 +30,7 @@ After creating Github action, Flank could reach more users.
 
 # Design
 
-There should be a possibility to specify all flank options using Github action variables as input, as well as passing the configuration itself.
+There should be a possibility to specify all flank options using GitHub action variables as input, as well as passing the configuration itself.
 
 User must provide at least:
 
@@ -41,13 +41,13 @@ User must provide at least:
 
 # API
 
-Flank Github action will be developed using [composite run steps action](https://docs.github.com/en/actions/creating-actions/creating-a-composite-run-steps-action) which just packs other actions and runs it as a single action.
+Flank GitHub action will be developed using [composite run steps action](https://docs.github.com/en/actions/creating-actions/creating-a-composite-run-steps-action) which just packs other actions and runs it as a single action.
 
 ### Design proposal
 
 ```yaml
 name: 'Flank'
-description: 'Run Flank from Github actions!'
+description: 'Run Flank from GitHub actions!'
 inputs:
     version: 
         description: 'Version of flank to run'
@@ -80,10 +80,10 @@ runs:
       run: <download flank>
       shell: bash
     - id: validate configuration
-      run: <check if configuation file or any options are specified>
+      run: <check if configuration file or any options are specified>
       shell: bash
     - id: run flank
-      run: <check if configuation file or any options are specified>
+      run: <check if configuration file or any options are specified>
       shell: bash
     - id: report
       run: <show run report to user>
@@ -143,15 +143,15 @@ jobs:
 
 # Results
 
-After finishing Flank GitHub actions should be published to [Github actions marketplace](https://github.com/marketplace?type=actions). 
+After finishing Flank GitHub actions should be published to [GitHub actions marketplace](https://github.com/marketplace?type=actions). 
 
 There should be also an announcement on Flank channel on Slack.
 
 The thing to consider is also using it for our internal verification together with integration tests
 
 # Dependencies
 
-Github action needs to have `action.yml` file in the root of the repository, however, Flank repository has the file for posting Slack message after release. However it is only used by Flank team, so it will be best to move it as a side repository and keep the main Flank action in Flank's mono repository
+GitHub action needs to have `action.yml` file in the root of the repository, however, Flank repository has the file for posting Slack message after release. However it is only used by Flank team, so it will be best to move it as a side repository and keep the main Flank action in Flank's mono repository
 
 # Testing
 

docs/flank-github-action/store_documentation.md

@@ -1,6 +1,6 @@
 ## Action
 
-This Github action allows for running Flank as a Github workflow.
+This GitHub action allows for running Flank as a GitHub workflow.
 
 Documentation for Flank is at [flank.github.io/flank](https://flank.github.io/flank/)