use windmill script instead of GH action to push changes (windmill-labs#837)

alpetric · hcourdent · web-flow · commit b4d1771ef380 · 2025-02-27T18:09:35.000+01:00
* use windmill script instead of GH action to push changes back to windmill

* Windmill syntax

---------

Co-authored-by: Henri Courdent &lt;122811744+hcourdent@users.noreply.github.com&gt;
diff --git a/docs/advanced/9_deploy_gh_gl/index.mdx b/docs/advanced/9_deploy_gh_gl/index.mdx
@@ -23,6 +23,13 @@ For all details on Deployments to prod in Windmill, see [Deploy to prod](../12_d
 The integration with git works in three-folds:
 
 1. [GitHub Action](https://docs.github.com/en/actions) + [CLI](../3_cli/index.mdx): upon any commit to a particular branch, the GitHub action will run the `wmill` CLI and push to a Windmill workspace this works using the CLI doing `wmill sync push` ([free & open source](/pricing)).
+
+:::tip
+
+You can also trigger a webhook and push the changes to Windmill using [this Windmill script](https://hub.windmill.dev/scripts/windmill/11414/git-sync-push-windmill) and pass the arguments as query args in the webhook triggered after pushing to the repo.
+
+:::
+
 2. [Git sync](../11_git_sync/index.mdx) (Workspace mode): Windmill automatically committing to a git repository upon any deployment to a workspace, this works using the CLI doing `wmill sync pull` ([Cloud and Enterprise Self-Hosted](/pricing)). Having it commit back to Windmill has 2 benefits:
 
     - It ensures that any automatically created metadata files are wrote-back (in case you pushed a script without its metadata for instance).
@@ -236,4 +243,4 @@ You are now ready to test the workflow. You can do so by:
 3. Check the target workspace in Windmill if the script has been deployed.
 4. Go to the runs page, toggle the "Sync" kind of jobs. You should see at least 2 jobs, one to push back your change to the staging (if set) workspace (no-op), and one to create a branch that targets the main branch (the one that will be merged).
 5. Now in your repository, you should see a new branch named wm_deploy/[WORKSPACE_NAME]/[SCRIPT_PATH] (for instance wm_deploy/staging/f/example/script).
-6. Merge that branch, now the changes should trigger the "Deploy to prod" GitHub action in the main branch.
+6. Merge that branch, now the changes should trigger the "Deploy to prod" GitHub action in the main branch.
