milestone: custom-scalars 🚀

.changesets/20250314T163021-pr-59.md

@@ -0,0 +1,9 @@
+---
+title: 'feat: email scalar'
+pr: 59
+author: jasonbahl
+type: feat
+breaking: false
+branch: milestone/custom-scalars
+---
+Pretend to add the Email Scalar

.changesets/20250314T163922-pr-60.md

@@ -0,0 +1,9 @@
+---
+title: 'feat: phone scalar'
+pr: 60
+author: jasonbahl
+type: feat
+breaking: false
+branch: milestone/custom-scalars
+---
+null

.changesets/20250314T164425-pr-61.md

@@ -0,0 +1,9 @@
+---
+title: 'feat!: breaking change'
+pr: 61
+author: jasonbahl
+type: other
+breaking: true
+branch: milestone/custom-scalars
+---
+Simulating a breaking change to test the workflows

.github/workflows/milestone-branch-workflow.md

@@ -50,7 +50,7 @@ When a PR is merged to a milestone branch, the changeset generation workflow:
 
 The workflow automatically creates and maintains a PR from the milestone branch to the develop branch:
 
-1. **PR Title**: `feat: feature-name 🚀`
+1. **PR Title**: `milestone: feature-name 🚀`
 2. **PR Body**: Contains:
    - Milestone information and progress
    - Link to the GitHub Milestone

automation-tests.php

@@ -16,3 +16,10 @@
 add_action( 'admin_notices', function() {
 	echo '<div class="notice notice-info"><p>😇 Automation Tests v' . AUTOMATION_TESTS_VERSION . '</p></div>';
 });
+
+// SCALARS:
+// - Email
+// - Phone
+
+// BREAKING CHANGE
+// We're simulating a breaking change with this comment.

docs/WORKFLOW_VISUALIZATION.md

@@ -244,7 +244,7 @@ graph TD
     D[Feature Branch 3] -->|Create PR| B
     B -->|Merge PR| E[Generate Changeset]
     E -->|Commit Changeset| B
-    B -->|Create/Update PR| F[develop]
+    B -->|Create/Update PR with title "milestone: feature-name 🚀"| F[develop]
     F -->|Merge PR| G[Generate Changeset]
     G -->|Commit Changeset| F
     F -->|Create/Update PR| H[main]