Skip to content

Conversation

@robertohuertasm
Copy link
Member

@robertohuertasm robertohuertasm commented Nov 5, 2025

What does this PR do? What is the motivation?

The Fix In Chat feature is also supported for VS Code so I removed the tabs.

Merge instructions

Merge readiness:

  • Ready for merge

For Datadog employees:

Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass 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.

[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.

Additional notes

IDE-5196

The feature is also supported for VS Code so I removed the tabs.
@robertohuertasm robertohuertasm requested a review from a team as a code owner November 5, 2025 12:42
Copy link
Contributor

@maycmlee maycmlee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@robertohuertasm thanks for opening this PR! Could you open a new PR with the branch name in the format of you_name/branch_name? It'll generate a staging preview.

@robertohuertasm
Copy link
Member Author

@maycmlee done! See #32715

@robertohuertasm robertohuertasm deleted the robertohuertasm-patch-2 branch November 10, 2025 11:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants