QUA-1518: Add PagerDuty feature

.pre-commit-config.yaml

@@ -3,4 +3,13 @@ repos:
     rev: v1.33.1
     hooks:
       - id: typos
-        args: ["--config", ".typos.toml"]
+        args: ["--config", ".typos.toml"]
+  - repo: local
+    hooks:
+      - id: mkdocs-warnings
+        name: mkdocs build (check for warnings)
+        entry: bash -c 'output=$(source venv/bin/activate && mkdocs build 2>&1); if echo "$output" | grep -q "WARNING"; then echo ""; echo "⚠️  MkDocs build produced warnings that might affect production:"; echo "$output" | grep "WARNING"; echo ""; fi; exit 0'
+        language: system
+        pass_filenames: false
+        always_run: true
+        verbose: true

docs/changelog-2023.md

@@ -806,8 +806,8 @@
 
     - ![Screenshot](assets/changelog/absolute-relative-change-limit.png#only-light){: style="height:100px"}
     ![Screenshot](assets/changelog/absolute-relative-change-limit.png#only-dark){: style="height:100px"}
-    - The [`Absolute Change Limit`](/data-quality-checks/metric-check.md#comparison-options/) check is designed to monitor changes in a field's value by a fixed amount. If the field's value changes by more than the specified limit since the last applicable scan, an anomaly is generated.
-    - The [`Relative Change Limit`](/data-quality-checks/metric-check.md#comparison-options/) check works similarly but tracks changes in terms of percentages. If the change in a field's value exceeds the defined percentage limit since the last applicable scan, an anomaly is generated.
+    - The [`Absolute Change Limit`](/data-quality-checks/metric-check.md#comparison-options) check is designed to monitor changes in a field's value by a fixed amount. If the field's value changes by more than the specified limit since the last applicable scan, an anomaly is generated.
+    - The [`Relative Change Limit`](/data-quality-checks/metric-check.md#comparison-options) check works similarly but tracks changes in terms of percentages. If the change in a field's value exceeds the defined percentage limit since the last applicable scan, an anomaly is generated.
 
 #### General Fixes
 

docs/cli/authentication.md

@@ -80,6 +80,7 @@ Environment variables take precedence over the config file. Combined with `QUALY
 
 ### GitHub Actions Example
 
+{% raw %}
 ```yaml
 jobs:
   quality-scan:
@@ -95,3 +96,4 @@ jobs:
         run: |
           qualytics operations scan --datastore-id 1 --background
 ```
+{% endraw %}

docs/cli/automation.md

@@ -71,6 +71,7 @@ qualytics operations scan --datastore-id 1 --background
 
 ### Quality Scan on Schedule
 
+{% raw %}
 ```yaml
 name: Nightly Quality Scan
 on:
@@ -93,9 +94,11 @@ jobs:
           qualytics operations profile --datastore-id ${{ vars.DATASTORE_ID }}
           qualytics operations scan --datastore-id ${{ vars.DATASTORE_ID }}
 ```
+{% endraw %}
 
 ### Config Promotion (Dev to Prod)
 
+{% raw %}
 ```yaml
 name: Promote Quality Config
 on:
@@ -123,9 +126,11 @@ jobs:
           qualytics config import --input ./qualytics-config --dry-run
           qualytics config import --input ./qualytics-config
 ```
+{% endraw %}
 
 ### Check Export and Import Across Environments
 
+{% raw %}
 ```yaml
 name: Sync Checks Dev → Staging
 on:
@@ -152,6 +157,7 @@ jobs:
           QUALYTICS_TOKEN: ${{ secrets.STAGING_QUALYTICS_TOKEN }}
         run: qualytics checks import --datastore-id ${{ vars.STAGING_DATASTORE_ID }} --input ./checks
 ```
+{% endraw %}
 
 ## Secrets Management
 

docs/cli/config-as-code.md

@@ -154,6 +154,7 @@ qualytics config import --input ./qualytics-config
 
 ### GitHub Actions Example
 
+{% raw %}
 ```yaml
 name: Promote Quality Config
 on:
@@ -188,3 +189,4 @@ jobs:
           DB_PASSWORD: ${{ secrets.PROD_DB_PASSWORD }}
         run: qualytics config import --input ./qualytics-config
 ```
+{% endraw %}

docs/explore/profiles.md

@@ -160,7 +160,7 @@ A modal window will appear, providing the options to create the tag. Enter the r
 
 ![create](../assets/explore/profiles/create-light.png)
 
-For more information on creating tags, refer to the [Add Tag section](../tags/overview-of-tag.md/#add-tag).
+For more information on creating tags, refer to the [Add Tag section](../tags/add-tag.md).
 
 ### Filter and Sort
 

docs/fields/field-status/concepts/field-status-lifecycle.md

@@ -14,10 +14,6 @@ flowchart LR
     Active -- User excludes the field --> Excluded
     Masked -- User excludes the field --> Excluded
     Excluded -- User restores the field --> Active
-
-    style Active fill:#4CAF50,color:#fff,stroke:#388E3C
-    style Masked fill:#FFA726,color:#fff,stroke:#F57C00
-    style Excluded fill:#EF5350,color:#fff,stroke:#C62828
 ```
 
 ## Automatic Transitions
@@ -33,12 +29,6 @@ flowchart LR
     Missing -- Field reappears in profile results --> Active
 
     Missing -- Permanently delete --> End(( ))
-
-    style Active fill:#4CAF50,color:#fff,stroke:#388E3C
-    style Masked fill:#FFA726,color:#fff,stroke:#F57C00
-    style Missing fill:#FFEE58,color:#000,stroke:#F9A825
-    style Start fill:#333,stroke:#333
-    style End fill:#333,stroke:#333
 ```
 
 ## Transition Details