-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Fix broken links to datadog-ci repo #31820
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
Conversation
tag: 'Documentation' | ||
text: 'Visualize your Error Tracking data in the Explorer' | ||
- link: 'https://github.com/DataDog/datadog-ci/tree/457d25821e838db9067dbe376d0f34fb1a197869/src/commands/sourcemaps' | ||
- link: 'https://github.com/DataDog/datadog-ci/tree/master/packages/datadog-ci/src/commands/sourcemaps' |
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.
This link wasn't broken, but adding a permalink can take users to a potentially outdated version of the repo.
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.
LGTM for RUM
…:DataDog/documentation into gabriel.anca/fix-datadog-ci-broken-links
I pushed a new commit because I'm about to merge DataDog/datadog-ci#1860, which will change the links to the 'deployment' plugin. I'll mark it as ready to merge as soon as that one is merged |
PR merged and the deployment links are now correct. Marked the PR as ready to merge! |
What does this PR do? What is the motivation?
Fixes multiple broken links. We are working on a migration in datadog-ci and many files have moved around.
Merge instructions
Merge readiness:
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