Skip to content

update reference of extra_ prefix for global_view_db#35927

Closed
lognarly wants to merge 4 commits intoDataDog:masterfrom
lognarly:lognarly/fix-global-view-db-ref
Closed

update reference of extra_ prefix for global_view_db#35927
lognarly wants to merge 4 commits intoDataDog:masterfrom
lognarly:lognarly/fix-global-view-db-ref

Conversation

@lognarly
Copy link
Copy Markdown
Contributor

What does this PR do? What is the motivation?

update reference of extra_ prefix for global_view_db to match rest of doc since it does not resolve

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.

AI assistance

Additional notes

@lognarly lognarly requested review from a team as code owners April 10, 2026 20:50
@git-thuerk-done
Copy link
Copy Markdown
Contributor

Hey @lognarly look good! Feel free to hit the squash and merge button once all those checks pass!

@lognarly
Copy link
Copy Markdown
Contributor Author

Hey @lognarly look good! Feel free to hit the squash and merge button once all those checks pass!

How do we get those other checks to run? Seems they are stuck?

@lognarly
Copy link
Copy Markdown
Contributor Author

@git-thuerk-done Just checking in once more here :)

@git-thuerk-done
Copy link
Copy Markdown
Contributor

Hi @lognarly sorry for the delay! It seems those checks didn't run because it looks like you created this PR off a fork rather than off the cloned docs repo itself! I just approved those and will merge shortly :)

@git-thuerk-done
Copy link
Copy Markdown
Contributor

Hi @lognarly Thank you for your contribution, and my apologies here but it seems we cannot merge a PR that was created from a fork, so you can either clone the repo locally and make your changes directly to this md file then push up a PR (gh repo clone DataDog/documentation) , or probably the easiest is to go to this page and click the "Edit" button, make your changes, then submit a fresh PR that way (be sure to use a / in the branch name such as lognarly/update-aurora-autodiscovery or something similar.

image

@lognarly
Copy link
Copy Markdown
Contributor Author

@git-thuerk-done The doc here mentions to fork the master branch, so perhaps this needs to be updated with new guidelines?

@lognarly
Copy link
Copy Markdown
Contributor Author

lognarly commented Apr 15, 2026

Also fwiw, this is how I've submitted PRs in the past as well. I went to go do what you mentioned from the UI as well, and it still mentions that its going to create a fork at the end of the day, so I think I end up in the same predicament?

@git-thuerk-done
Copy link
Copy Markdown
Contributor

Ah interesting! Sorry for the confusion, I wonder if something else then was going on with this branch as certainly the required checks weren't passing. If you don't mind putting up a new PR we'll be sure to get your updated merged in :)

@lognarly
Copy link
Copy Markdown
Contributor Author

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.

2 participants