Manual publish workflow

[michaelclapham]

Allow publishing from any branch (for deploying test versions before committing to main)

This can be helpful for testing template changes whilst switching between PR's.

For example, if a native developer is working on a change for which there is a draft PR open in templates, and wants someone else to test their native changes, currently the steps are:

Dev 1 and Dev 2 both have to

• Check out native branch that needs testing
• Point native package.json mobile-apps-article-templates to ../../mobile-apps-article-templates
• Check out templates branch that needs testing
• Run npm run build in mobile-apps-article-templates
• Rebuild native app

After this workflow the steps would be

Dev 1.

• Make templates changes
• Create testing release using this new workflow. Similar to this one
• Point native package.json mobile-apps-article-templates to testing version e.g 1.0.805-testing1
• Share branch with dev 2 or create draft pull request

Dev 2 (on iOS and Android)

• Check out dev 1's native branch that needs testing
• Build and run

or Dev 2 (on Android only)

• Run ./scripts/run_pr_debug.sh 1234 for PR number 1234 that contains changes that need testing.