DOCSP-50728 Java Sync Write/Read Redirects

[mballard-mdb]

Pull Request Info

Fix write/read redirects to include links like the one on Jira.

Slack conversation

PR Reviewing Guidelines

JIRA - https://jira.mongodb.org/browse/DOCSP-50728

Staging Links

No pages to preview

Self-Review Checklist

• Is this free of any warnings or errors in the RST?
• Did you run a spell-check?
• Did you run a grammar-check?
• Are all the links working?
• Are the facets and meta keywords accurate?
• Are the page titles greater than 20 characters long and SEO relevant?

[netlify]

✅ Deploy Preview for docs-java ready!

Name	Link
🔨 Latest commit	0491a7a
🔍 Latest deploy log	https://app.netlify.com/projects/docs-java/deploys/686c29b32e97fa0009290681
😎 Deploy Preview	https://deploy-preview-718--docs-java.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[docs-builder-bot]

🔄 Deploy Preview for docs-java processing

Item	Details
🔨 Latest Commit	213f778ab4532aada71a069129f2fbaed78f7b60
😎 Deploy Preview	https://deploy-preview-718--docs-java.netlify.app
🔍 Build Logs	View Logs

[jordan-smith721]

LGTM

[github-actions]

The backport to v5.2 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v5.2 v5.2
# Navigate to the new working tree
cd .worktrees/backport-v5.2
# Create a new branch
git switch --create backport-718-to-v5.2
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 f87bd9d575eda7fdfcf5c4591cc41760b1fc67ba
# Push it to GitHub
git push --set-upstream origin backport-718-to-v5.2
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v5.2

Then, create a pull request where the base branch is v5.2 and the compare/head branch is backport-718-to-v5.2.

[github-actions]

The backport to v5.1 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v5.1 v5.1
# Navigate to the new working tree
cd .worktrees/backport-v5.1
# Create a new branch
git switch --create backport-718-to-v5.1
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 f87bd9d575eda7fdfcf5c4591cc41760b1fc67ba
# Push it to GitHub
git push --set-upstream origin backport-718-to-v5.1
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v5.1

Then, create a pull request where the base branch is v5.1 and the compare/head branch is backport-718-to-v5.1.

[github-actions]

The backport to v5.0 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v5.0 v5.0
# Navigate to the new working tree
cd .worktrees/backport-v5.0
# Create a new branch
git switch --create backport-718-to-v5.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 f87bd9d575eda7fdfcf5c4591cc41760b1fc67ba
# Push it to GitHub
git push --set-upstream origin backport-718-to-v5.0
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v5.0

Then, create a pull request where the base branch is v5.0 and the compare/head branch is backport-718-to-v5.0.

[github-actions]

The backport to v5.4 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v5.4 v5.4
# Navigate to the new working tree
cd .worktrees/backport-v5.4
# Create a new branch
git switch --create backport-718-to-v5.4
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 f87bd9d575eda7fdfcf5c4591cc41760b1fc67ba
# Push it to GitHub
git push --set-upstream origin backport-718-to-v5.4
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v5.4

Then, create a pull request where the base branch is v5.4 and the compare/head branch is backport-718-to-v5.4.

[github-actions]

The backport to v5.5 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v5.5 v5.5
# Navigate to the new working tree
cd .worktrees/backport-v5.5
# Create a new branch
git switch --create backport-718-to-v5.5
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 f87bd9d575eda7fdfcf5c4591cc41760b1fc67ba
# Push it to GitHub
git push --set-upstream origin backport-718-to-v5.5
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v5.5

Then, create a pull request where the base branch is v5.5 and the compare/head branch is backport-718-to-v5.5.

[mballard-mdb]

💔 Some backports could not be created

Status	Branch	Result
✅	v5.5
✅	v5.4
❌	v5.3	Conflict resolution was aborted by the user
❌	v5.2	Conflict resolution was aborted by the user
❌	v5.1	Conflict resolution was aborted by the user
❌	v5.0	Conflict resolution was aborted by the user

Note: Successful backport PRs will be merged automatically after passing CI.

Manual backport

To create the backport manually run:

backport --pr 718

Questions ?

Please refer to the Backport tool documentation