Update Dynatrace documentation links #38706
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
spring-projects-issues
added
the
status: waiting-for-triage
wilkinsona
requested changes
Dec 7, 2023
spring-boot-project/spring-boot-docs/src/docs/asciidoc/attributes.adoc
Outdated
Show resolved
Hide resolved
|
Please update the base branch to 3.1.x. The 2.7.x (and 3.0.x) branches are now read-only as OSS support has ended. |
pirgeo
force-pushed
the
update-dynatrace-doc-links
branch
from
2978a7e to
e2ebe93
Compare
|
Rebased onto |
philwebb
added
type: documentation
wilkinsona
approved these changes
Dec 7, 2023
|
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At Dynatrace, the documentation URLs now have an overhauled format, including new shortlinks. This PR swaps out the "old" links with the new style of shortlink in the documentation.
I based this PR on 2.7.x, since the docs for that are still up (and 2.7 is still in commercial support IIUC). Will these changes be merged forward? Or should I just create a PR based on 3.1.x instead, since that is the officially supported version?