[release/9.1] Improve default codespace experience with devcontainer.json location change#7706
Merged
danmoseley merged 1 commit intorelease/9.1from Feb 20, 2025
Merged
Conversation
…ault codespace experience.
danmoseley
approved these changes
Feb 20, 2025
github-actions
bot
added
the
needs-area-label
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Backport of #7704 to release/9.1
/cc @mitchdenny
Customer Impact
None. This impacts contributors to our repo. This is making it easier to test the release/9.1 branch (just keeping it in line with main).
Testing
It's the same devcontainer file, just moved to a location so that the GitHub UX will pick it up as the default when you create a codespace instead of creating a codespace using the default codespaces image which is not useful for us.
Risk
Low.
Regression?