DOCSP-46753 Change Go driver Count Documents duplicate title

[shuangela]

Pull Request Info

PR Reviewing Guidelines

JIRA - https://jira.mongodb.org/browse/DOCSP-46753
Staging - https://deploy-preview-426--docs-golang.netlify.app/usage-examples/count/

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?

[netlify]

✅ Deploy Preview for docs-golang ready!

Name	Link
🔨 Latest commit	9e822ac
🔍 Latest deploy log	https://app.netlify.com/sites/docs-golang/deploys/67bf94ead96e4e00088d2488
😎 Deploy Preview	https://deploy-preview-426--docs-golang.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 site configuration.

[lindseymoore]

Is the title "Count Document Methods" to short? Or perhaps "Count Document Method Examples"? Would prefer not to have Usage Example in the title as that is the section name, and the rest of the pages don't have it, so it seems inconsistent.

[shuangela]

Is the title "Count Document Methods" to short? Or perhaps "Count Document Method Examples"? Would prefer not to have Usage Example in the title as that is the section name, and the rest of the pages don't have it, so it seems inconsistent.

I'm not sure about count document methods because the other page also is talking about the count document method. I think Count Document Method Examples is good, I'll make a change!

[lindseymoore]

Great, LGTM!

[sarahemlin]

@shuangela let's leave the URL in place on this one. Thank you!

[github-actions]

The backport to v2.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-v2.0 v2.0
# Navigate to the new working tree
cd .worktrees/backport-v2.0
# Create a new branch
git switch --create backport-426-to-v2.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 29c9d3679e64df41a1b5759cb714988b25e015ed
# Push it to GitHub
git push --set-upstream origin backport-426-to-v2.0
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.0

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

[github-actions]

The backport to v1.15 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-v1.15 v1.15
# Navigate to the new working tree
cd .worktrees/backport-v1.15
# Create a new branch
git switch --create backport-426-to-v1.15
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 29c9d3679e64df41a1b5759cb714988b25e015ed
# Push it to GitHub
git push --set-upstream origin backport-426-to-v1.15
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.15

Then, create a pull request where the base branch is v1.15 and the compare/head branch is backport-426-to-v1.15.

[github-actions]

The backport to v1.17 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-v1.17 v1.17
# Navigate to the new working tree
cd .worktrees/backport-v1.17
# Create a new branch
git switch --create backport-426-to-v1.17
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 29c9d3679e64df41a1b5759cb714988b25e015ed
# Push it to GitHub
git push --set-upstream origin backport-426-to-v1.17
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.17

Then, create a pull request where the base branch is v1.17 and the compare/head branch is backport-426-to-v1.17.

[github-actions]

The backport to v1.16 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-v1.16 v1.16
# Navigate to the new working tree
cd .worktrees/backport-v1.16
# Create a new branch
git switch --create backport-426-to-v1.16
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 29c9d3679e64df41a1b5759cb714988b25e015ed
# Push it to GitHub
git push --set-upstream origin backport-426-to-v1.16
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.16

Then, create a pull request where the base branch is v1.16 and the compare/head branch is backport-426-to-v1.16.

[github-actions]

The backport to v1.13 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-v1.13 v1.13
# Navigate to the new working tree
cd .worktrees/backport-v1.13
# Create a new branch
git switch --create backport-426-to-v1.13
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 29c9d3679e64df41a1b5759cb714988b25e015ed
# Push it to GitHub
git push --set-upstream origin backport-426-to-v1.13
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.13

Then, create a pull request where the base branch is v1.13 and the compare/head branch is backport-426-to-v1.13.

[github-actions]

The backport to v1.12 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-v1.12 v1.12
# Navigate to the new working tree
cd .worktrees/backport-v1.12
# Create a new branch
git switch --create backport-426-to-v1.12
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 29c9d3679e64df41a1b5759cb714988b25e015ed
# Push it to GitHub
git push --set-upstream origin backport-426-to-v1.12
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.12

Then, create a pull request where the base branch is v1.12 and the compare/head branch is backport-426-to-v1.12.

[github-actions]

The backport to v1.14 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-v1.14 v1.14
# Navigate to the new working tree
cd .worktrees/backport-v1.14
# Create a new branch
git switch --create backport-426-to-v1.14
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 29c9d3679e64df41a1b5759cb714988b25e015ed
# Push it to GitHub
git push --set-upstream origin backport-426-to-v1.14
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.14

Then, create a pull request where the base branch is v1.14 and the compare/head branch is backport-426-to-v1.14.

[github-actions]

The backport to v1.14 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-v1.14 v1.14
# Navigate to the new working tree
cd .worktrees/backport-v1.14
# Create a new branch
git switch --create backport-426-to-v1.14
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 29c9d3679e64df41a1b5759cb714988b25e015ed
# Push it to GitHub
git push --set-upstream origin backport-426-to-v1.14
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.14

Then, create a pull request where the base branch is v1.14 and the compare/head branch is backport-426-to-v1.14.

[github-actions]

The backport to v2.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-v2.0 v2.0
# Navigate to the new working tree
cd .worktrees/backport-v2.0
# Create a new branch
git switch --create backport-426-to-v2.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 29c9d3679e64df41a1b5759cb714988b25e015ed
# Push it to GitHub
git push --set-upstream origin backport-426-to-v2.0
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.0

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

[github-actions]

The backport to v1.17 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-v1.17 v1.17
# Navigate to the new working tree
cd .worktrees/backport-v1.17
# Create a new branch
git switch --create backport-426-to-v1.17
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 29c9d3679e64df41a1b5759cb714988b25e015ed
# Push it to GitHub
git push --set-upstream origin backport-426-to-v1.17
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.17

Then, create a pull request where the base branch is v1.17 and the compare/head branch is backport-426-to-v1.17.

[github-actions]

The backport to v1.12 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-v1.12 v1.12
# Navigate to the new working tree
cd .worktrees/backport-v1.12
# Create a new branch
git switch --create backport-426-to-v1.12
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 29c9d3679e64df41a1b5759cb714988b25e015ed
# Push it to GitHub
git push --set-upstream origin backport-426-to-v1.12
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.12

Then, create a pull request where the base branch is v1.12 and the compare/head branch is backport-426-to-v1.12.

[github-actions]

The backport to v1.15 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-v1.15 v1.15
# Navigate to the new working tree
cd .worktrees/backport-v1.15
# Create a new branch
git switch --create backport-426-to-v1.15
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 29c9d3679e64df41a1b5759cb714988b25e015ed
# Push it to GitHub
git push --set-upstream origin backport-426-to-v1.15
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.15

Then, create a pull request where the base branch is v1.15 and the compare/head branch is backport-426-to-v1.15.

[github-actions]

The backport to v1.13 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-v1.13 v1.13
# Navigate to the new working tree
cd .worktrees/backport-v1.13
# Create a new branch
git switch --create backport-426-to-v1.13
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 29c9d3679e64df41a1b5759cb714988b25e015ed
# Push it to GitHub
git push --set-upstream origin backport-426-to-v1.13
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.13

Then, create a pull request where the base branch is v1.13 and the compare/head branch is backport-426-to-v1.13.

[github-actions]

The backport to v1.16 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-v1.16 v1.16
# Navigate to the new working tree
cd .worktrees/backport-v1.16
# Create a new branch
git switch --create backport-426-to-v1.16
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 29c9d3679e64df41a1b5759cb714988b25e015ed
# Push it to GitHub
git push --set-upstream origin backport-426-to-v1.16
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.16

Then, create a pull request where the base branch is v1.16 and the compare/head branch is backport-426-to-v1.16.

[shuangela]

💔 Some backports could not be created

Status	Branch	Result
✅	v2.0
✅	v1.17
✅	v1.16
✅	v1.15
✅	v1.14
✅	v1.13
✅	v1.12
❌	v1.11	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 426

Questions ?

Please refer to the Backport tool documentation