Add Public NuGet Feed to Support Developers Without Private Feed Access #396
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ss (#393) * change feed * add internal back * update the order * remove internal one * update the template * add comments back * remove another one
…ples into user/leilzh/changefeed
alexlamtest
approved these changes
Dec 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cherry-pick from 43a876e
Description
The original NuGet feed lacked public access support. To address this, a new public NuGet feed has been created under the shine-oss organization, utilizing the WinAppSDK Samples project. This feed now serves the WinAppSDK Samples repository, ensuring full open-source compliance and accessibility.
the Feed Link: https://dev.azure.com/shine-oss/WinAppSDK-Samples/_artifacts/feed/WinAppSDK-SampleDeps
Target Release
main branch
Checklist
/azp run SamplesCI-<FeatureName>to have the CI build run on my branch for each of my FeatureName my PR is modifying. This must be done on the latest commit on the PR before merging to ensure the build is up to date and accurate. Warning: the PR will not block automatically if this is not run due to '/azp run' limitation on triggering more than 10 pipelines.