[migration] Update current
branch for APM agent docs
#3185
Merged
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.
Follow up to #3173
We're migrating the latest major version of each APM agent's docs from AsciiDoc to Markdown. Because of the way APM agent teams manage release branches, it's important that they are able to force push from
main
to the latest major version branch.In the initial migration PRs (https://github.com/elastic/docs-eng-team/issues/130), we deleted AsciiDoc files and added Markdown files to
main
. We should also do the same for the latest major version to make it easier for engineers to make changes to the latest version. But, if we delete the AsciiDoc files on the latest major version branch, we need to pull AsciiDoc files from a different branch for the next ~3 weeks (until the Markdown docs are live onelastic.co
).I created a new
do-not-delete_legacy-docs
branch off the latest major version branch in each apm-agent-* repo. We can use this temporary branch to continue publishing AsciiDoc docs until the new docs are live.@bmorelli25 feel free to correct me and/or elaborate if I missed anything!