Add GitHub Actions Workflow for Basic CoastSat Testing with ee

[thekester]

As discussed in this GitHub issue and with the support of @jdbcode, the process for authenticating Earth Engine in GitHub Actions has been updated. The recommended protocol is now available in the official repository of the Google Earth Engine Community, which will soon include updates for enhanced security like using one of the three methods recommended by Google.

You can check an implementation in one of my repositories here, although this method is considered one of the less secure options and should be used as a last resort.

[kvos]

hi @thekester, looks really good. so how can we test these GitHub actions and get notified if something is broken?

[thekester]

hi @thekester, looks really good. so how can we test these GitHub actions and get notified if something is broken?

Hi @kvos!

To start testing GitHub Actions with Earth Engine in Python, follow these steps:

1. Initialize Earth Engine in GitHub Actions
   Begin by setting up Earth Engine according to the instructions for initializing Earth Engine in Python with GitHub Actions. This setup will allow your GitHub Action workflows to authenticate and use Earth Engine resources.

2. Create a New Branch
   It's a good idea to create a dedicated branch for testing these workflows. This way, you can safely iterate and debug without affecting your main project branch.

3. Test the Workflow
   Once you’ve set up the initial workflow, push changes to your branch. GitHub will automatically trigger the workflow, and you’ll be able to observe its performance and get notified of any issues.

4. Enhance with a Non-Interactive Coastsat Script
   Once the Earth Engine setup is stable, you can further optimize your workflow by creating a non-interactive version of the Coastsat script. This will help streamline execution, particularly for automated processes within GitHub Actions.

Following this approach will enable continuous integration checks via GitHub, ensuring that any issues or breaks in the workflow are quickly caught. Let me know if you need any further assistance with this!

[kvos]

@thekester , sorry for the delay I haven't had time to try this out. Will check it soon.