🚀 CI/CD - Create separate workflow for testing branches for Tina

CC: @bradystroud

The Pain 🤕🩼

Testing branches for the tina migration is a nightmare. Building locally against the main content branch can take 40+ minutes and occasionally fails because JavaScript runs out of memory. Developers are also unable to work on other PBIs while waiting for branches to build, forcing them to work on other tasks such as email tasks.

The solution 💡

If we can create a pipeline that deploys separately from the others we can easily test deployments before merging and without having to build locally. This affectively unblocks developers by allowing them to test their PBI against large content branches using the deployment workflow while working on separate PBIs locally.

Acceptance criteria

• Storage account approved by a Sysadmin
• Tina test workflow has a manual workflow dispatch
• Tina workflow does not affect any other deployment environment for SSW people
• The test workflow contains a parameters allowing developers to specify a target content branch for rules

Start by reviewing the repository's existing deployment workflows and the Tina migration setup. Confirm how a manual Tina test workflow can target a content branch without affecting other deployment environments, then work through the storage-account approval and each acceptance criterion.