Aaron Parker

Thinking about how to implement this. The simplest approach might be to get `Get-GitHubRepoRelease` to check for an environment variable call `GITHUB_TOKEN`. That way it would work when a token...

Support for a token stored in `GITHUB_TOKEN` added in 83c605b495e60b3bc4acccb2878f6b1a6e05c56c. Tests OK.

I've been thinking about what should be returned - should we throw when encountering an issue, or display a warning and move onto the next download so that we don't...

I think the consideration here, is what's the best approach when using Evergreen in an image build or packaging factory pipeline. Perhaps it's best to leave error catching to who...

Pushed another update to `development` that should now support the following, allowing the function to continue even in the event of an error. ```powershell Get-EvergreenApp -Name MozillaFirefox -ErrorAction "Ignore" -WarningAction...

There's a fix in place for this for the latest release; however, this might need some review later if the vendor is chaning URLs around etc.

This is a known issue documented here: https://stealthpuppy.com/evergreen/issues/#errors-and-warnings

If you use Fiddler to capture Opera checking for an update, it might provide something on their update API.

@Deyda nice, thanks. You can see an initial set of help files here for `en-US`: [https://github.com/aaronparker/Evergreen/tree/development/help/en-US](https://github.com/aaronparker/Evergreen/tree/development/help/en-US). This would be using platyPS to general MAML help from this markdown. German help...

Support for `en-US` added in ddd5aa2996d431b8c7abc2e2ec9e6679a6496a39