Update to latest

Author: AlexanderSehr

docs/content/contributing/bicep/bicep-contribution-flow/_index.md

@@ -425,6 +425,18 @@ If you're working on a new module, we'd also ask you to create its corresponding
 
 {{% /expand %}}
 
+{{% notice style="tip" %}}
+
+The workflow is configured in a way that it will trigger on any changes in Upstream's (i.e., `Azure/bicep-registry-modules`) `main` branch if they may have an impact on the module or its validation. However, while in a fork, the workflow will stop right after initiation thanks to the condition:
+```yml
+# Only run if not canceled and not in a fork, unless triggered by a workflow_dispatch event
+if: ${{ !cancelled() && !(github.repository != 'Azure/bicep-registry-modules' && github.event_name != 'workflow_dispatch') }}
+```
+This condition ensures that you don't accidently trigger a large amount of module workflows when e.g., merging changes from upstream into your fork.
+
+{{% /notice %}}
+
+
 {{% notice style="tip" %}}
 
 After any change to a module and before running tests, we highly recommend running the [Set-AVMModule]({{% siteparam base %}}/contributing/bicep/bicep-contribution-flow/generate-bicep-module-files) utility to update all module files that are auto-generated (e.g., the `main.json` & `readme.md` files).

docs/static/includes/avm.workflow.template.yml

@@ -53,6 +53,7 @@ jobs:
   job_initialize_pipeline:
     runs-on: ubuntu-latest
     name: "Initialize pipeline"
+    if: ${{ !cancelled() && !(github.repository != 'Azure/bicep-registry-modules' && github.event_name != 'workflow_dispatch') }}
     steps:
       - name: "Checkout"
         uses: actions/checkout@v5