Skip to content

DOCSP-50028 Remove EOL mentions #153

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
May 23, 2025

Conversation

lindseymoore
Copy link
Contributor

@lindseymoore lindseymoore commented May 22, 2025

Pull Request Info

PR Reviewing Guidelines

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

Staging Links

  • aggregation
  • connect/connection-options
  • connect/stable-api
  • data-formats/time-series
  • read/collations
  • security/auth-mechanisms/aws-iam
  • security/auth-mechanisms/scram
  • security/in-use-encryption
  • 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?

    Copy link

    netlify bot commented May 22, 2025

    Deploy Preview for docs-ruby ready!

    Name Link
    🔨 Latest commit 0b4ce17
    🔍 Latest deploy log https://app.netlify.com/projects/docs-ruby/deploys/682fcb8f08dadb0008ed9b06
    😎 Deploy Preview https://deploy-preview-153--docs-ruby.netlify.app
    📱 Preview on mobile
    Toggle QR Code...

    QR Code

    Use your smartphone camera to open QR code link.

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

    Copy link
    Collaborator

    @norareidy norareidy left a comment

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    LGTM + one comment

    @lindseymoore lindseymoore merged commit 97876e6 into mongodb:master May 23, 2025
    5 checks passed
    Copy link
    Contributor

    The backport to v2.21 failed:

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

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

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

    Copy link
    Contributor

    The backport to v2.20 failed:

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

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

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

    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    2 participants