-
Notifications
You must be signed in to change notification settings - Fork 756
Add details of interactions between notifications and loops #597
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
Conversation
This clarifies behaviour raised in ansible/ansible#81950 and ansible/ansible#77550 as expected and documented.
gotmax23
left a comment
There was a problem hiding this 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!
|
@lod, are you still interested in proceeding with this PR? |
Co-authored-by: Maxwell G <[email protected]>
|
@gotmax23 - i committed your suggested edits. Can you take another look and approve the PR if you agree? |
|
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 The 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. |
Make the loop trigger even more explicit.
|
Thanks @felixfontein @samccann and @gotmax23 I incorporated the suggestions and resynced it against the current devel. |
|
Thanks for refreshing this PR and continuing with the changes @lod |
oraNod
left a comment
There was a problem hiding this 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 🚀
Backport to stable-2.15: 💚 backport PR created✅ Backport PR branch: Backported as #2063 🤖 @patchback |
* 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)
Backport to stable-2.14: 💚 backport PR created✅ Backport PR branch: Backported as #2064 🤖 @patchback |
* 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)
Backport to stable-2.16: 💚 backport PR created✅ Backport PR branch: Backported as #2065 🤖 @patchback |
* 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)
Backport to stable-2.17: 💚 backport PR created✅ Backport PR branch: Backported as #2066 🤖 @patchback |
* 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)
Backport to stable-2.18: 💚 backport PR created✅ Backport PR branch: Backported as #2067 🤖 @patchback |
* 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)
…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]>
…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]>
…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]>
…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]>
…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]>
* 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]>
This clarifies behaviour raised in ansible/ansible#81950 and ansible/ansible#77550 as expected and documented.