Skip to content

Conversation

@spetersenms
Copy link
Contributor

❔What, Why & How

Refactor that puts all handling of DeployTo settings into the ReadSettings action instead of letting Deploy and DetermineDeploymentEnvironments handle it.

Related to issue: #

✅ Checklist

  • Add tests (E2E, unit tests)
  • Update RELEASENOTES.md
  • Update documentation (e.g. for new settings or scenarios)
  • Add telemetry

$settings.projectName = $project # Default to project path as project name
}

$ghEnvironments = @(GetGitHubEnvironments)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will be called on every ReadSettings call, right? Given that GetGitHubEnvironments makes an HTTP call, it seems excessive and unnecessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants