Add global continuousDeployment setting

Scenarios/settings.md

@@ -131,6 +131,7 @@ The repository settings are only read from the repository settings file (.github
 | <a id="enableTaskScheduler"></a>enableTaskScheduler | Setting enableTaskScheduler to true in your project setting file, causes the build container to be created with the Task Scheduler running. | false |
 | <a id="useCompilerFolder"></a>useCompilerFolder | Setting useCompilerFolder to true causes your pipelines to use containerless compiling. Unless you also set **doNotPublishApps** to true, setting useCompilerFolder to true won't give you any performance advantage, since AL-Go for GitHub will still need to create a container in order to publish and test the apps. In the future, publishing and testing will be split from building and there will be other options for getting an instance of Business Central for publishing and testing. **Note** when using UseCompilerFolder you need to sign apps using the new signing mechanism described [here](../Scenarios/Codesigning.md). | false |
 | <a id="excludeEnvironments"></a>excludeEnvironments | excludeEnvironments can be an array of GitHub Environments, which should be excluded from the list of environments considered for deployment. github-pages is automatically added to this array and cannot be used as environment for deployment of AL-Go for GitHub projects. | [ ] |
+| <a id="continuousDeployment"></a>continuousDeployment | Global default for continuous deployment. When set, this overrides the per-environment default (which is based on environment name conventions), but is itself overridden by any per-environment **DeployTo\<environmentname>.ContinuousDeployment** setting. Set to **false** to disable automatic CD for all environments globally — for example in an organization settings variable — while still allowing manual deployment via the **Publish To Environment** workflow. Per-environment settings can then opt back in by setting `DeployTo<name>: { continuousDeployment: true }`. | (not set — falls back to per-environment name convention) |
 | <a id="trustMicrosoftNuGetFeeds"></a>trustMicrosoftNuGetFeeds | Unless this setting is set to false, AL-Go for GitHub will trust the NuGet feeds provided by Microsoft. The feeds provided by Microsoft contains all Microsoft apps, all Microsoft symbols and symbols for all AppSource apps. | true |
 | <a id="trustedNuGetFeeds"></a>trustedNuGetFeeds | trustedNuGetFeeds can be an array of NuGet feed specifications, which AL-Go for GitHub will use for dependency resolution. Every feed specification must include a URL property and can optionally include a few other properties:<br />**url** = The URL of the feed (examples: https://pkgs.dev.azure.com/myorg/apps/\_packaging/myrepo/nuget/v3/index.json or https://nuget.pkg.github.com/mygithuborg/index.json").<br />**authTokenSecret** = If the NuGet feed specified by URL is private, the authTokenSecret must be the name of a secret containing the authentication token with permissions to search and read packages from the NuGet feed.<br />**patterns** = AL-Go for GitHub will only trust packages, where the ID matches this pattern. Default is all packages (\*).<br />**fingerprints** = If specified, AL-Go for GitHub will only trust packages signed with a certificate with a fingerprint matching one of the fingerprints in this array. | [ ] |
 | <a id="nuGetFeedSelectMode"></a>nuGetFeedSelectMode | Determines the select mode when finding Business Central app packages from NuGet feeds, based on the dependency version specified in app.json. Options are:<br/>- `Earliest` for earliest version of the package<br/>- `EarliestMatching` for earliest version of the package also compatible with the Business Central version used<br/>- `Exact` for the exact version of the package<br/>- `Latest` for the latest version of the package<br/>- `LatestMatching` for the latest version of the package also compatible with the Business Central version used. | LatestMatching |