🚀 Pre-alpha state. A platform designed for building enterprise-grade, multi-tenant products using Azure, .NET, React, TypeScript, Infrastructure as Code, etc.
Ensure that when running the configure-continuous-deployments CLI command on a newly forked/cloned repository, GitHub workflows are enabled. Due to a recent change in GitHub, the CLI can no longer start a workflow using gh workflow run to enable workflows automatically. Now, if workflows are not enabled, a browser is opened, and the user must enable workflows before the CLI continues.
The configure-continuous-deployments CLI command has been updated to replace the null-conditional operator in Config?.Path with the null-forgiving operator Config!.Path. All GitHub CLI commands now explicitly specify the GitHub repository. Additionally, method names in the configure-continuous-deployments CLI command have been refined for consistency and clarity.
Checklist
[x] I have added a Label to the pull-request
[x] I have added tests, and done manual regression tests
[x] I have updated the documentation, if necessary
Summary & Motivation
Ensure that when running the
configure-continuous-deploymentsCLI command on a newly forked/cloned repository, GitHub workflows are enabled. Due to a recent change in GitHub, the CLI can no longer start a workflow usinggh workflow runto enable workflows automatically. Now, if workflows are not enabled, a browser is opened, and the user must enable workflows before the CLI continues.The
configure-continuous-deploymentsCLI command has been updated to replace the null-conditional operator inConfig?.Pathwith the null-forgiving operatorConfig!.Path. All GitHub CLI commands now explicitly specify the GitHub repository. Additionally, method names in theconfigure-continuous-deploymentsCLI command have been refined for consistency and clarity.Checklist