Skip to content

Comments

Migrate RTD URLs to docs.ansible.com#1473

Merged
gundalow merged 1 commit intoansible:develfrom
gundalow:fix-rtd-url-migration
Nov 18, 2025
Merged

Migrate RTD URLs to docs.ansible.com#1473
gundalow merged 1 commit intoansible:develfrom
gundalow:fix-rtd-url-migration

Conversation

@gundalow
Copy link
Contributor

Summary

This PR updates readthedocs.io URLs to their docs.ansible.com equivalents with proper anchor preservation.

Changes (23 unique URLs, 33 files updated)

Technical Details

  • ✅ Anchor fragments preserved during URL transformations
  • ✅ HTTP redirects followed to final destinations
  • ✅ URL validation completed before applying changes
  • ✅ Configuration-driven URL mapping system

🤖 Generated with Claude Code

Co-Authored-By: Claude noreply@anthropic.com

@github-actions github-actions bot added docs Changes to documentation needs_triage New item that needs to be triaged labels Nov 11, 2025
@gundalow gundalow force-pushed the fix-rtd-url-migration branch from c88038e to 6a94c9c Compare November 11, 2025 19:24
🤖 Generated with Claude Code
https://claude.ai/code

Co-Authored-By: Claude <noreply@anthropic.com>
@gundalow gundalow force-pushed the fix-rtd-url-migration branch from 6a94c9c to 7abd345 Compare November 11, 2025 19:33
@gundalow gundalow marked this pull request as ready for review November 18, 2025 12:19
@gundalow gundalow requested a review from a team as a code owner November 18, 2025 12:19
@gundalow gundalow merged commit af2d547 into ansible:devel Nov 18, 2025
18 checks passed
@gundalow gundalow deleted the fix-rtd-url-migration branch November 18, 2025 12:21
@Shrews Shrews added backport-2.4 Request Patchback to create a PR using `git cherry-pick -x` and removed needs_triage New item that needs to be triaged labels Feb 24, 2026
@patchback
Copy link

patchback bot commented Feb 24, 2026

Backport to release_2.4: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply af2d547 on top of patchback/backports/release_2.4/af2d54740162e8c4837be908a311237adb503b03/pr-1473

Backporting merged PR #1473 into devel

  1. Ensure you have a local repo clone of your fork. Unless you cloned it
    from the upstream, this would be your origin remote.
  2. Make sure you have an upstream repo added as a remote too. In these
    instructions you'll refer to it by the name upstream. If you don't
    have it, here's how you can add it:
    $ git remote add upstream https://github.com/ansible/ansible-runner.git
  3. Ensure you have the latest copy of upstream and prepare a branch
    that will hold the backported code:
    $ git fetch upstream
    $ git checkout -b patchback/backports/release_2.4/af2d54740162e8c4837be908a311237adb503b03/pr-1473 upstream/release_2.4
  4. Now, cherry-pick PR Migrate RTD URLs to docs.ansible.com #1473 contents into that branch:
    $ git cherry-pick -x af2d54740162e8c4837be908a311237adb503b03
    If it'll yell at you with something like fatal: Commit af2d54740162e8c4837be908a311237adb503b03 is a merge but no -m option was given., add -m 1 as follows instead:
    $ git cherry-pick -m1 -x af2d54740162e8c4837be908a311237adb503b03
  5. At this point, you'll probably encounter some merge conflicts. You must
    resolve them in to preserve the patch from PR Migrate RTD URLs to docs.ansible.com #1473 as close to the
    original as possible.
  6. Push this branch to your fork on GitHub:
    $ git push origin patchback/backports/release_2.4/af2d54740162e8c4837be908a311237adb503b03/pr-1473
  7. Create a PR, ensure that the CI is green. If it's not — update it so that
    the tests and any other checks pass. This is it!
    Now relax and wait for the maintainers to process your pull request
    when they have some cycles to do reviews. Don't worry — they'll tell you if
    any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

@Shrews Shrews removed the backport-2.4 Request Patchback to create a PR using `git cherry-pick -x` label Feb 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Changes to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants