Skip to content

Conversation

@lod
Copy link
Contributor

@lod lod commented Oct 12, 2023

This clarifies behaviour raised in ansible/ansible#81950 and ansible/ansible#77550 as expected and documented.

This clarifies behaviour raised in ansible/ansible#81950 and ansible/ansible#77550 as expected and documented.
@github-actions github-actions bot added the needs_triage Needs a first human triage before being processed. label Oct 12, 2023
@gotmax23 gotmax23 added the new_contributor This PR is the first contribution by a new community member. label Oct 13, 2023
Copy link
Collaborator

@gotmax23 gotmax23 left a comment

Choose a reason for hiding this comment

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

I left some initial feedback. Thanks for the contribution!

@gotmax23 gotmax23 added the needs_info requesting more detail from OP label Nov 24, 2023
@gotmax23
Copy link
Collaborator

@lod, are you still interested in proceeding with this PR?

@samccann samccann removed needs_info requesting more detail from OP needs_triage Needs a first human triage before being processed. labels Jan 18, 2024
@samccann
Copy link
Contributor

@gotmax23 - i committed your suggested edits. Can you take another look and approve the PR if you agree?

@oraNod
Copy link
Contributor

oraNod commented Sep 12, 2024

Hi @lod We've made some changes to the underlying readthedocs project for this repository. I'm going to close and re-open this issue to kick off a new PR preview build.

You might notice there will be two checks for readthedocs. One for docs/readthedocs.org:stage-ansible-core and another for docs/readthedocs.org:ansible-core.

The stage-ansible-core check is for the old project and will result in a 404. Please ignore that and use the ansible-core check only.

Thank you for your patience and understanding. Also thanks for your contribution to the Ansible documentation. If you have any questions or concerns, please do let us know either here, in the docs channel on Matrix, or in the Ansible forum. Cheers.

@oraNod oraNod closed this Sep 12, 2024
@oraNod oraNod reopened this Sep 12, 2024
Make the loop trigger even more explicit.
@lod
Copy link
Contributor Author

lod commented Oct 16, 2024

Thanks @felixfontein @samccann and @gotmax23

I incorporated the suggestions and resynced it against the current devel.

@oraNod oraNod added backport-2.17 Automatically create a backport for the stable-2.17 branch backport-2.18 Automatically create a backport for the stable-2.18 branch labels Oct 24, 2024
@oraNod
Copy link
Contributor

oraNod commented Oct 24, 2024

Thanks for refreshing this PR and continuing with the changes @lod

Copy link
Contributor

@oraNod oraNod left a comment

Choose a reason for hiding this comment

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

Thanks for the docs contribution @lod 🚀

@oraNod oraNod merged commit 74b2c95 into ansible:devel Oct 25, 2024
@patchback
Copy link

patchback bot commented Oct 25, 2024

Backport to stable-2.15: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.15/74b2c95dd4a13db21b167de9bb72f7287f679841/pr-597

Backported as #2063

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

patchback bot pushed a commit that referenced this pull request Oct 25, 2024
* Add details of interactions between notifications and loops

This clarifies behaviour raised in ansible/ansible#81950 and ansible/ansible#77550 as expected and documented.

* Apply suggestions from code review

Co-authored-by: Maxwell G <[email protected]>

* Incorporate suggestions from @felixfontein

Make the loop trigger even more explicit.

---------

Co-authored-by: Sandra McCann <[email protected]>
Co-authored-by: Maxwell G <[email protected]>
(cherry picked from commit 74b2c95)
@patchback
Copy link

patchback bot commented Oct 25, 2024

Backport to stable-2.14: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.14/74b2c95dd4a13db21b167de9bb72f7287f679841/pr-597

Backported as #2064

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

patchback bot pushed a commit that referenced this pull request Oct 25, 2024
* Add details of interactions between notifications and loops

This clarifies behaviour raised in ansible/ansible#81950 and ansible/ansible#77550 as expected and documented.

* Apply suggestions from code review

Co-authored-by: Maxwell G <[email protected]>

* Incorporate suggestions from @felixfontein

Make the loop trigger even more explicit.

---------

Co-authored-by: Sandra McCann <[email protected]>
Co-authored-by: Maxwell G <[email protected]>
(cherry picked from commit 74b2c95)
@patchback
Copy link

patchback bot commented Oct 25, 2024

Backport to stable-2.16: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.16/74b2c95dd4a13db21b167de9bb72f7287f679841/pr-597

Backported as #2065

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

patchback bot pushed a commit that referenced this pull request Oct 25, 2024
* Add details of interactions between notifications and loops

This clarifies behaviour raised in ansible/ansible#81950 and ansible/ansible#77550 as expected and documented.

* Apply suggestions from code review

Co-authored-by: Maxwell G <[email protected]>

* Incorporate suggestions from @felixfontein

Make the loop trigger even more explicit.

---------

Co-authored-by: Sandra McCann <[email protected]>
Co-authored-by: Maxwell G <[email protected]>
(cherry picked from commit 74b2c95)
@patchback
Copy link

patchback bot commented Oct 25, 2024

Backport to stable-2.17: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.17/74b2c95dd4a13db21b167de9bb72f7287f679841/pr-597

Backported as #2066

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

patchback bot pushed a commit that referenced this pull request Oct 25, 2024
* Add details of interactions between notifications and loops

This clarifies behaviour raised in ansible/ansible#81950 and ansible/ansible#77550 as expected and documented.

* Apply suggestions from code review

Co-authored-by: Maxwell G <[email protected]>

* Incorporate suggestions from @felixfontein

Make the loop trigger even more explicit.

---------

Co-authored-by: Sandra McCann <[email protected]>
Co-authored-by: Maxwell G <[email protected]>
(cherry picked from commit 74b2c95)
@patchback
Copy link

patchback bot commented Oct 25, 2024

Backport to stable-2.18: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.18/74b2c95dd4a13db21b167de9bb72f7287f679841/pr-597

Backported as #2067

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

patchback bot pushed a commit that referenced this pull request Oct 25, 2024
* Add details of interactions between notifications and loops

This clarifies behaviour raised in ansible/ansible#81950 and ansible/ansible#77550 as expected and documented.

* Apply suggestions from code review

Co-authored-by: Maxwell G <[email protected]>

* Incorporate suggestions from @felixfontein

Make the loop trigger even more explicit.

---------

Co-authored-by: Sandra McCann <[email protected]>
Co-authored-by: Maxwell G <[email protected]>
(cherry picked from commit 74b2c95)
oraNod pushed a commit that referenced this pull request Oct 25, 2024
…2067)

* Add details of interactions between notifications and loops

This clarifies behaviour raised in ansible/ansible#81950 and ansible/ansible#77550 as expected and documented.

* Apply suggestions from code review

Co-authored-by: Maxwell G <[email protected]>

* Incorporate suggestions from @felixfontein

Make the loop trigger even more explicit.

---------

Co-authored-by: Sandra McCann <[email protected]>
Co-authored-by: Maxwell G <[email protected]>
(cherry picked from commit 74b2c95)

Co-authored-by: David Tulloh <[email protected]>
oraNod pushed a commit that referenced this pull request Oct 25, 2024
…2065)

* Add details of interactions between notifications and loops

This clarifies behaviour raised in ansible/ansible#81950 and ansible/ansible#77550 as expected and documented.

* Apply suggestions from code review

Co-authored-by: Maxwell G <[email protected]>

* Incorporate suggestions from @felixfontein

Make the loop trigger even more explicit.

---------

Co-authored-by: Sandra McCann <[email protected]>
Co-authored-by: Maxwell G <[email protected]>
(cherry picked from commit 74b2c95)

Co-authored-by: David Tulloh <[email protected]>
oraNod pushed a commit that referenced this pull request Oct 25, 2024
…2063)

* Add details of interactions between notifications and loops

This clarifies behaviour raised in ansible/ansible#81950 and ansible/ansible#77550 as expected and documented.

* Apply suggestions from code review

Co-authored-by: Maxwell G <[email protected]>

* Incorporate suggestions from @felixfontein

Make the loop trigger even more explicit.

---------

Co-authored-by: Sandra McCann <[email protected]>
Co-authored-by: Maxwell G <[email protected]>
(cherry picked from commit 74b2c95)

Co-authored-by: David Tulloh <[email protected]>
oraNod pushed a commit that referenced this pull request Oct 25, 2024
…2064)

* Add details of interactions between notifications and loops

This clarifies behaviour raised in ansible/ansible#81950 and ansible/ansible#77550 as expected and documented.

* Apply suggestions from code review

Co-authored-by: Maxwell G <[email protected]>

* Incorporate suggestions from @felixfontein

Make the loop trigger even more explicit.

---------

Co-authored-by: Sandra McCann <[email protected]>
Co-authored-by: Maxwell G <[email protected]>
(cherry picked from commit 74b2c95)

Co-authored-by: David Tulloh <[email protected]>
oraNod pushed a commit that referenced this pull request Oct 25, 2024
…2066)

* Add details of interactions between notifications and loops

This clarifies behaviour raised in ansible/ansible#81950 and ansible/ansible#77550 as expected and documented.

* Apply suggestions from code review

Co-authored-by: Maxwell G <[email protected]>

* Incorporate suggestions from @felixfontein

Make the loop trigger even more explicit.

---------

Co-authored-by: Sandra McCann <[email protected]>
Co-authored-by: Maxwell G <[email protected]>
(cherry picked from commit 74b2c95)

Co-authored-by: David Tulloh <[email protected]>
oraNod pushed a commit that referenced this pull request Nov 25, 2024
* Add details of interactions between notifications and loops

This clarifies behaviour raised in ansible/ansible#81950 and ansible/ansible#77550 as expected and documented.

* Apply suggestions from code review

Co-authored-by: Maxwell G <[email protected]>

* Incorporate suggestions from @felixfontein

Make the loop trigger even more explicit.

---------

Co-authored-by: Sandra McCann <[email protected]>
Co-authored-by: Maxwell G <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-2.17 Automatically create a backport for the stable-2.17 branch backport-2.18 Automatically create a backport for the stable-2.18 branch new_contributor This PR is the first contribution by a new community member.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants