Skip to content

Actions: dotnet/install-scripts

Actions

Issue Labeler

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
labeler.yml
35 workflow runs
35 workflow runs

Filter by Event

⌥ + click/return to exclude

Filter by Status

⌥ + click/return to exclude

Filter by Branch

⌥ + click/return to exclude

Filter by Actor

⌥ + click/return to exclude
Unable to download sdk Issue Labeler #43: Issue #741 opened by ness31
6s
6s
There doesn't seem to be a way to install ASP.NET Core Windows Hosting Bundle Issue Labeler #42: Issue #735 opened by catmanjan
6s
6s
Add a proper changelog Issue Labeler #41: Issue #734 opened by Frulfump
15s
15s
The script failed to execute due to hash mismatch Issue Labeler #40: Issue #729 opened by geniuszxy
9s
9s
Signing failing after upgrade to .NET 10 Issue Labeler #38: Issue #716 opened by ellahathaway
10s
10s
Running dotnet-install.sh from MINGW64 is not supported Issue Labeler #37: Issue #715 opened by DrewMcArthur
12s
12s
Official pipeline broken: PublishBuildArtifacts@1 no longer allowed by 1ES Pipeline Templates Issue Labeler #36: Issue #712 opened by MichaelSimons
9s
9s
CI pipelines should use repo build scripts instead of UseDotNet@2 Issue Labeler #35: Issue #706 opened by MichaelSimons
8s
8s
Upgrade to xUnit v3 Issue Labeler #34: Issue #705 opened by MichaelSimons
8s
8s
Update test project to target net10.0 Issue Labeler #33: Issue #704 opened by MichaelSimons
15s
15s
Duplicate test cases in runtime install tests cause 24 skipped tests per run Issue Labeler #32: Issue #701 opened by MichaelSimons
7s
7s
PR validation Windows leg takes ~50 minutes Issue Labeler #31: Issue #699 opened by MichaelSimons
9s
9s
Test run names are ambiguous in CI Issue Labeler #30: Issue #698 opened by MichaelSimons
9s
9s
is_dotnet_package_installed "already installed" check is weaker than the .NET host visibility check, leading to un-healable broken installations Issue Labeler #29: Issue #694 opened by nmoinvaz
7s
7s
Incorrect 10.0.5 tried to be downloaded Issue Labeler #28: Issue #689 opened by Frulfump
9s
9s
Improve output for unsupported one-part channel in dotnet-install.sh Issue Labeler #27: Issue #686 opened by ellahathaway
14s
14s
Install using channel-only on Mac M4 for dotnet 10 fails Issue Labeler #26: Issue #685 opened by tillig
17s
17s
What does "only when sourcing script" mean? Issue Labeler #25: Issue #683 opened by bartonjs
8s
8s
[Draft] New Issue - Awaiting More Details Issue Labeler #24: Issue #679 opened by netai878888-afk
7s
7s
AL2023 Linux failed to install DotNet 10 on manual attempt Issue Labeler #23: Issue #678 opened by genifycom
9s
9s
dotnet-install does not handle redirects when downloading the product version files Issue Labeler #22: Issue #670 opened by mmitche
9s
9s
Integration Tests Should be Updated after .NET preview1 and GA Releases Issue Labeler #21: Issue #665 opened by ellahathaway
11s
11s
MacOS Tests Timing Out Issue Labeler #20: Issue #663 opened by ellahathaway
13s
13s
Corrupt dotnet binary exits with exit code 137 after installing .NET 10 Issue Labeler #19: Issue #662 opened by chrishaland
7s
7s
Failed tests swallow exception message in GivenThatIWantToInstallDotnetFromAScript.Dispose() Issue Labeler #18: Issue #659 opened by PhilippNaused
7s
7s