-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[DOCS-10227] VS Code extension revamp #28826
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
base: master
Are you sure you want to change the base?
Conversation
Preview links (active after the
|
Actually doesn't look like we use this image any longer, but I didn't fully confirm this so putting it back just in case...
This is what I meant to delete...
- Various edits - Add Cursor to nav menu - Update some images - Replace original image (for caching issues): view-in-vscode.png
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for the work @joepeeples! Left some comments here.
FYI some screenshots are outdated or would benefit from better consistency (e.g. same background color and theme), I'll create new ones. I think we should move forward without them though.
Co-authored-by: ThibaultK <Vomain@users.noreply.github.com>
Created docs card for review: https://datadoghq.atlassian.net/browse/DOCS-10801 |
Datadog Summary✅ Code Quality ✅ Code Security ✅ Dependencies Was this helpful? Give us feedback! |
What does this PR do? What is the motivation?
Reorganizes and revises the product docs for Datadog's VS Code extension. Also brings attention to compatibility with Cursor and other forks & flavors.
Merge instructions
Merge readiness:
For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the
<name>/<description>
convention and include the forward slash (/
). Without this format, your pull request will not pass in CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
To have your PR automatically merged after it receives the required reviews, add the following PR comment:
Additional notes