search

ansible / ansible-documentation

Ansible community documentation
https://docs.ansible.com/
GNU General Public License v3.0
63 stars 369 forks source link

Update playbooks_loops.rst #1617

Closed Japje closed 2 weeks ago

Japje commented 2 weeks ago

update example to correct typo

ansible-documentation-bot[bot] commented 2 weeks ago

Thanks for your Ansible docs contribution! We talk about Ansible documentation on matrix at #docs:ansible.im and on libera IRC at #ansible-docs if you ever want to join us and chat about the docs! We meet there on Tuesdays (see the Ansible calendar) and welcome additions to our weekly agenda items - scroll down to find the upcoming agenda and add a comment to put something new on that agenda.

patchback[bot] commented 2 weeks ago

Backport to stable-2.15: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.15/6f223211643283594f87010f20678a7736e62239/pr-1617

Backported as https://github.com/ansible/ansible-documentation/pull/1619

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

samccann commented 2 weeks ago

Thanks @Japje for the Ansible docs fix and welcome to the Ansible project!

patchback[bot] commented 2 weeks ago

Backport to stable-2.16: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 6f223211643283594f87010f20678a7736e62239 on top of patchback/backports/stable-2.16/6f223211643283594f87010f20678a7736e62239/pr-1617

Backporting merged PR #1617 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-documentation.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/stable-2.16/6f223211643283594f87010f20678a7736e62239/pr-1617 upstream/stable-2.16
  4. Now, cherry-pick PR #1617 contents into that branch: 
    $ git cherry-pick -x 6f223211643283594f87010f20678a7736e62239

    If it'll yell at you with something like fatal: Commit 6f223211643283594f87010f20678a7736e62239 is a merge but no -m option was given., add -m 1 as follows instead:

    $ git cherry-pick -m1 -x 6f223211643283594f87010f20678a7736e62239
  5. At this point, you'll probably encounter some merge conflicts. You must resolve them in to preserve the patch from PR #1617 as close to the original as possible.
  6. Push this branch to your fork on GitHub: 
    $ git push origin patchback/backports/stable-2.16/6f223211643283594f87010f20678a7736e62239/pr-1617
  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.

patchback[bot] commented 2 weeks ago

Backport to stable-2.17: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.17/6f223211643283594f87010f20678a7736e62239/pr-1617

Backported as https://github.com/ansible/ansible-documentation/pull/1620

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