Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: align recommended vscode and devcontainer extensions #17207

Merged
merged 2 commits into from Aug 16, 2022

Conversation

Shegox
Copy link
Contributor

@Shegox Shegox commented Aug 16, 2022

Changes

This PR aligns the VsCode extensions found in the devcontainer with the ones recommended using the .vscode/extensions.json file

Context

While experimenting with both devcontainers/CodeSpaces as well as local dev environment I found that there are some differences in the configuration for both. This PR aligns them and makes sure that as a developer you have a similar experience using a devcontainer or a local development environment.

I tested the changes against in my local VsCode as well as on a local devcontainer.

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please tick one)

I have verified these changes via:

  • Code inspection only, or
  • Newly added/modified unit tests, or
  • No unit tests but ran on a real repository, or
  • Both unit tests + ran on a real repository

@viceice viceice changed the title fix: align recommended vscode and devcontainer extensions chore: align recommended vscode and devcontainer extensions Aug 16, 2022
@viceice viceice enabled auto-merge (squash) August 16, 2022 08:01
@viceice viceice merged commit 8453cdf into renovatebot:main Aug 16, 2022
@renovate-release
Copy link
Collaborator

🎉 This PR is included in version 32.160.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants