Merge branch 'main' into patch-2

.devcontainer/devcontainer.json

@@ -33,6 +33,13 @@
 
 	// Use 'forwardPorts' to make a list of ports inside the container available locally.
 	"forwardPorts": [4000],
+		
+	"portsAttributes": {
+		"4000": {
+        		"label": "Preview",
+        		"onAutoForward": "openPreview"
+      		}
+	},
 
 	// Use 'postCreateCommand' to run commands after the container is created.
 	"postCreateCommand": "git lfs pull && npm ci",

content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md

@@ -86,6 +86,16 @@ If you confirm a secret is real and that you intend to fix it later, you should
 
 {% data reusables.secret-scanning.push-protection-multiple-branch-note %}
 
+{% ifversion ghes < 3.6 or ghae < 3.6 %}
+
+{% tip %}
+
+**Tip:** You can use {% data variables.product.prodname_secret_scanning %} as a push protection from the web UI, as well as the command line, in {% data variables.product.product_name %} version 3.6 or later.
+
+{% endtip %}
+
+{% endif %}
+
 ### Allowing a blocked secret to be pushed
 
 If {% data variables.product.prodname_dotcom %} blocks a secret that you believe is safe to push, you can allow the secret and specify the reason why it should be allowed.
@@ -137,4 +147,5 @@ If you confirm a secret is real and that you intend to fix it later, you should
 
 1. Click **Allow secret**.
 
+
 {% endif %}