Test that e2e doesn't run on doc-only PRs

.github/pull_request_template.md

@@ -3,6 +3,9 @@
  <!-- Please label this pull request according to what type of issue you are addressing (see ../CONTRIBUTING.md) -->
 **What type of PR is this?**
 
+THIS IS A BOGUS CHANGE
+
+
 <!--
 Add one of the following kinds:
 /kind feature

OWNERS_ALIASES

@@ -2,6 +2,7 @@
 
 aliases:
   sig-cluster-lifecycle-leads:
+    - boguschange
     - fabriziopandini
     - justinsb
     - neolit123

Tiltfile

@@ -6,6 +6,7 @@ helm_cmd = "./hack/tools/bin/helm"
 kind_cmd = "./hack/tools/bin/kind"
 tools_bin = "./hack/tools/bin"
 
+# THIS IS A BOGUS CHANGE
 #Add tools to path
 os.putenv("PATH", os.getenv("PATH") + ":" + tools_bin)
 

docs/Makefile

@@ -17,6 +17,7 @@ ROOT_DIR:=$(shell dirname $(realpath $(lastword $(MAKEFILE_LIST))))
 SOURCES := $(shell find ${ROOT_DIR} -name \*.plantuml)
 DIAGRAMS := $(SOURCES:%.plantuml=%.png)
 
+# THIS IS A BOGUS CHANGE
 # Hosts running SELinux need :z added to volume mounts
 SELINUX_ENABLED := $(shell cat /sys/fs/selinux/enforce 2> /dev/null || echo 0)
 

docs/book/src/roadmap.md

@@ -1,6 +1,8 @@
 # Cluster API Azure Roadmap
 
-The best place to see what's coming is in [the public milestones](https://github.com/kubernetes-sigs/cluster-api-provider-azure/milestones).  
+THIS IS A BOGUS CHANGE
+
+The best place to see what's coming is in [the public milestones](https://github.com/kubernetes-sigs/cluster-api-provider-azure/milestones).
 The next numbered milestone (e.g. **1.8**) is planned at the very beginning of the 2-month release cycle. This planning and discussion begins at [Cluster API Azure Office Hours](http://bit.ly/k8s-capz-agenda) after a major release.
 Active community PR contributions are prioritized throughout the release, but unplanned work will arise. Hence the items in the milestone are a rough estimate which may change.
 The "next" milestone is a very rough collection of issues for the milestone after the current numbered one to help prioritize upcoming work.
@@ -11,9 +13,9 @@ CAPZ is the official production-ready Cluster API implementation to administer t
 
 ## Epics
 
-There are a number of large priority "Epics" which may span across milestones which we believe are important to providing CAPZ users an even better experience and improving the vision.  
+There are a number of large priority "Epics" which may span across milestones which we believe are important to providing CAPZ users an even better experience and improving the vision.
 
--  Latest Core Dependencies - The foundation should keep everything under a supported version of dependencies as well as to enable the latest features. 
+-  Latest Core Dependencies - The foundation should keep everything under a supported version of dependencies as well as to enable the latest features.
     - Includes: [track 2 go-sdk](https://github.com/kubernetes-sigs/cluster-api-provider-azure/issues/2670), [Azure Service Operator (ASO)](https://github.com/kubernetes-sigs/cluster-api-provider-azure/issues/416), 100% [k8s out-of-tree Azure provider](https://github.com/kubernetes-sigs/cluster-api-provider-azure/issues/715)
 -  ManagedClusters - Provisioning new AKS (ManagedClusters) clusters at scale is a common use case we want to enable an excellent experience with stability and all of the same features available in AKS.
     - Includes: [ManagedClusters E2E Tests](https://github.com/kubernetes-sigs/cluster-api-provider-azure/issues/2873), [ClusterClass support](https://github.com/kubernetes-sigs/cluster-api-provider-azure/issues/2684), [Enabling all AKS features](https://github.com/kubernetes-sigs/cluster-api-provider-azure/issues/2625), [Evolution of standardized CAPI ManagedCluster for CAPZ](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/proposals/20220725-managed-kubernetes.md)

exp/README.md

@@ -1,6 +1,6 @@
 # exp
 
-This subrepository holds experimental code and API types.
+This subrepository holds experimental code and API types. THIS IS A BOGUS CHANGE.
 
 **Warning**: Packages here are experimental and unreliable. Some may one day be promoted to the main repository, or they may be modified arbitrarily or even disappear altogether.
 

hack/observability/readme.md

@@ -1,5 +1,7 @@
 # Observability
 
+THIS IS A BOGUS CHANGE
+
 During development of CAPZ, it's become clear log messages can only tell part of the debugging
 story. As the code becomes more complex, we need better tools to help us understand what is
 happening in the controller.

netlify.toml

@@ -1,3 +1,4 @@
+# THIS IS A BOGUS CHANGE
 # Netlify build instructions
 [build]
     command = "./docs/book/install-and-build.sh"

tilt-provider.json

@@ -1,5 +1,5 @@
 {
-  "name": "azure",
+  "name": "azure-BOGUSCHANGE",
   "config": {
     "image": "gcr.io/k8s-staging-cluster-api-azure/cluster-api-azure-controller",
     "live_reload_deps": [