-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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
point at corresponding version #59200
Conversation
CI failures seem unrelated to the changes. Kicking off a new run. |
I published this branch to the test site and went to compare the old/bad/wrong behavior in prod against the new/good/correct behavior introduced by this PR . . . and now I can't replicate the bug. In the module docs, the |
@acozine you would have to use stable branches to reproduce the issue:
which is 'correct' for now, but once 2.9 is released .. it won't be with PR i get
which should 'always' be true |
I thought this behavior happened in the published docs as well, and happened in +1 to merging this fix. When 2.9 comes out we can test the behavior in the published docs again. |
I'm curious as to why the condtional on |
@akatch that was existing, i just refactored the 'common parts' out of it, so took 11 lines down to 3 |
Got it. shipit
|
modules were always pointing at latest
fixes #54736
ISSUE TYPE
COMPONENT NAME
ansible-doc