Merge pull request #13 from kevingrismore/feat/update-proj-1

changes to project 1

.github/workflows/project-1-deploy.yaml

@@ -7,6 +7,7 @@ on:
   pull_request:
     types:
       - opened
+      - synchronize
     paths:
       - "project_1/**"
   push:

.github/workflows/project-2-deploy.yaml

@@ -7,6 +7,7 @@ on:
   pull_request:
     types:
       - opened
+      - synchronize
     paths:
       - "project_2/**"
   push:

README.md

@@ -3,8 +3,8 @@ This is an advanced example for managing CI/CD across multiple Prefect workspace
 The GitHub Actions workflows in this repo: 
 - create mirrored deployments across staging and prod workspaces
     - which workspace flows are deployed to is determined by the branch that changes happen on:
-        - a pull request on any branch updates deployments in the staging workspace
-        - a merge to `main` updates deployments in the prod workspace
+        - opening a pull request on any branch, as well as commits to an open pull request, will update deployments in the staging workspace
+        - a merge to `main` will update deployments in the prod workspace
 - build and push docker images that do _not_ contain flow code, and are tagged like `:<commit-hash>-<environment>` to tie the code version and branch/env to image versions
 - cache both docker image layers and pip dependencies for ultra fast rebuilds
 - push code to S3 (via the `push` step of each `prefect.yaml`), where:

project_1/flow.py

@@ -4,6 +4,7 @@
 @flow(log_prints=True)
 def hello():
     print("Hello from Project 1! :)")
+    print("new addition to project 1")
 
 
 if __name__ == "__main__":

project_1/requirements.txt

@@ -1,2 +1,2 @@
-prefect==2.16.1
+prefect==3.1.0
 prefect-aws