Sync partner_templates branch with main (#1184)

* Added Cloudrail according to instructions and existing examples

* Adding Cloudrail according to documentation and examples

* Oops

* Add original Fortify on Demand workflow

* Update Fortify on Demand workflow

* Update Fortify on Demand supported languages

* Add 3rd-party GitHub Actions disclaimer

* Sysdig Secure Inline Scan with SARIF report to starter workflows

* Added some extra comments, Github Actions V2 and changed env vars

* Reviews from PR #1110

* Adding 'Dockerfile' to category list

* Update according to PR review comments

* File renames as requested in PR comments

* Revert "Azure Data Factory CI starter workflow (#1111)" (#1146)

This reverts commit 7f30309cce.

* use env variables for user-set values (#1117)

Co-authored-by: Josh Gross <[email protected]>

* Apply suggestions from nickfyson's code review

Co-authored-by: Nick Fyson <[email protected]>

* removing "deployment" templates from sync-ghes (#1127)

* Update code-scanning/properties/sysdig-scan.properties.json

Co-authored-by: Nick Fyson <[email protected]>

* Update code-scanning/properties/sysdig-scan.properties.json

Co-authored-by: Nick Fyson <[email protected]>

* Changed svg logo

* Rename sysdig.svg to sysdig-scan.svg

* Switched svg logo (again) for a better fit

* Rename fortify.json to fortify.properties.json

* Correct character-case of "c" in Cloudrail

* AWS template also used Docker

* trigger on push instead of release (#1157)

Co-authored-by: Josh Gross <[email protected]>

* Added new templates for 3 clouds.

* Revert "Added new templates for 3 clouds."

This reverts commit c765d6316f.

* Add workflow for Microsoft C++ Code Analysis

* Updated action to meet guidelines

* correct typo in msvc.properties.json

Co-authored-by: Yoni Leitersdorf <[email protected]>
Co-authored-by: Ruud Senden <[email protected]>
Co-authored-by: Ruud Senden <[email protected]>
Co-authored-by: Manuel Boira Cuevas <[email protected]>
Co-authored-by: manuelbcd <[email protected]>
Co-authored-by: Nick Fyson <[email protected]>
Co-authored-by: Sarah Edwards <[email protected]>
Co-authored-by: Josh Gross <[email protected]>
Co-authored-by: Aparna Ravindra <[email protected]>
Co-authored-by: manuelbcd <[email protected]>
Co-authored-by: Daniel Winsor <[email protected]>

deployments/azure.yml

@@ -1,4 +1,4 @@
-# This workflow will build and push a node.js application to an Azure Web App when a release is created.
+# This workflow will build and push a node.js application to an Azure Web App when there is a push to the $default-branch branch.
 #
 # This workflow assumes you have already created the target Azure App Service web app.
 # For instructions see https://docs.microsoft.com/azure/app-service/app-service-plan-manage#create-an-app-service-plan
@@ -16,8 +16,9 @@
 # For more information on GitHub Actions for Azure, refer to https://github.com/Azure/Actions
 # For more samples to get started with GitHub Action workflows to deploy to Azure, refer to https://github.com/Azure/actions-workflow-samples
 on:
-  release:
-    types: [created]
+  push:
+    branches:
+      - $default-branch
 
 env:
   AZURE_WEBAPP_NAME: your-app-name    # set this to your application's name