DX: Add setup guide for using VS Code Dev Containers#6318
DX: Add setup guide for using VS Code Dev Containers#6318
Conversation
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6318 +/- ##
=======================================
Coverage 49.84% 49.84%
=======================================
Files 1824 1824
Lines 80899 80899
Branches 7178 7178
=======================================
Hits 40328 40328
Misses 39015 39015
Partials 1556 1556 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Great job! No new security vulnerabilities introduced in this pull request |
withinfocus
left a comment
There was a problem hiding this comment.
bitwarden/contributing-docs#154 never got finished but we should get that done. The approach we've been using with documentation in repos is that the close-to-code content is about the component such as how it works and how an owning team would work on and maintain it; the contributing docs is for how to use it. This means that most of this content needs to show up in the other PR.




📔 Objective
I didn't know we had suport for dev containers and there were some setup steps that I stumbled upon and needed help to solve. I've documented what I think is the process, but I'm more than happy with edits.
Once this is merged we can also link to it from the contributing guidelines.
📸 Screenshots
⏰ Reminders before review
🦮 Reviewer guidelines
:+1:) or similar for great changes:memo:) or ℹ️ (:information_source:) for notes or general info:question:) for questions:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:) for suggestions / improvements:x:) or:warning:) for more significant problems or concerns needing attention:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt:pick:) for minor or nitpick changes