Add link to Android doc #114977
Merged
Add link to Android doc #114977
Conversation
This file contains hidden or 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
There was a problem hiding this comment.
Pull Request Overview
This PR updates the OS onboarding documentation by refining the explanation under the "Other" section and adding a new link to the Android testing documentation.
- Updated wording for the description of other environments.
- Added a link to the Android testing documentation.
|
Tagging subscribers to this area: @dotnet/area-meta |
jkotas
approved these changes
Apr 23, 2025
Co-authored-by: Jan Kotas <[email protected]>
carlossanlop
approved these changes
Apr 25, 2025
|
/ba-g Looks like Build Analysis is waiting for any CI leg to start, but it won't happen because this PR is only editing a markdown file. @dotnet/dnceng looks like a minor bug, can you take a look? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
In response to #112885