@@ -24,7 +24,7 @@ micromamba install conda-forge::earthengine-api
2424command. Use ` --force ` to ensure that the auth flow is triggered and new credentials are
2525written. If a browser is detected, it'll have you go online to complete authentication;
2626follow the prompts. If a browser is not available, see
27- [ alternatives] ( [url]( https://developers.google.com/earth-engine/guides/auth#authentication_details) ) .
27+ [ alternatives] ( https://developers.google.com/earth-engine/guides/auth#authentication_details ) .
2828
2929``` shell
3030earthengine authenticate --force
@@ -86,7 +86,7 @@ in the step that runs my Earth Engine script** ([ee-test-with-oauth2.py](https:/
8686
8787## 4. Initialize to Earth Engine in your test file
8888
89- In the test file ([ee-test-with-oauth2.py](https://github.com/gee-community/ee-initialize-github-actions/blob/main/ee-test-with-oauth2.py)
89+ In the test file ([ee-test-with-oauth2.py](https://github.com/gee-community/ee-initialize-github-actions/blob/main/ee-test-with-oauth2.py))
9090that makes Earth Engine requests, **construct Oauth2 credentials
9191from the credentials info in the secret**. The credentials info is fetched from
9292the environment variable we set previously, and then arranged as arguments
@@ -116,11 +116,11 @@ print(ee.String("Greetings from the Earth Engine servers!").getInfo())
116116# # 5. Test the script
117117
118118In this case, I'm just **manually triggering the workflow from the "Actions" tab,
119- clicking on the workflow and running the workflow**.
119+ clicking on the workflow, and running the workflow**.
120120
121121
122122
123- As you can see the scripts runs successfully and we get a nice message from the
123+ As you can see, the scripts runs successfully and we get a nice message from the
124124Earth Engine servers 😁
125125
126126
0 commit comments