Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Little glitch in the Tests page #76449

Closed
1 task done
b-enoit-be opened this issue Dec 2, 2021 · 1 comment · Fixed by #76539
Closed
1 task done

Little glitch in the Tests page #76449

b-enoit-be opened this issue Dec 2, 2021 · 1 comment · Fixed by #76539
Labels
affects_2.13 docs This issue/PR relates to or includes documentation. has_pr This issue has an associated PR. support:core This issue/PR relates to code supported by the Ansible Engineering Team.

Comments

@b-enoit-be
Copy link
Contributor

b-enoit-be commented Dec 2, 2021 •
edited

Summary

In the page https://docs.ansible.com/ansible/latest/user_guide/playbooks_tests.html, and more specifically in the section https://docs.ansible.com/ansible/latest/user_guide/playbooks_tests.html#testing-if-a-list-value-is-true, the version in which the feature has been added seems to be above the title, when it should be below it.

If someone confirms me that

New in version 2.4.

indeed relates to

Testing if a list value is True

Then, I'd be happy to open a PR fixing it.

Issue Type

Documentation Report

Component Name

docs/docsite/rst/user_guide/playbooks_tests.rst

Ansible Version

latest in the docs

Additional Information

Makes is clear that the version stated indeed relates to the section Testing if a list value is True and not to the above section Testing if a list contains a value

Code of Conduct

  • I agree to follow the Ansible Code of Conduct
@ansibot
Copy link
Contributor

ansibot commented Dec 2, 2021

Files identified in the description:

If these files are incorrect, please update the component name section of the description or use the !component bot command.

click here for bot help

@ansibot ansibot added affects_2.13 docs This issue/PR relates to or includes documentation. needs_triage Needs a first human triage before being processed. support:core This issue/PR relates to code supported by the Ansible Engineering Team. labels Dec 2, 2021
@mkrizek mkrizek removed the needs_triage Needs a first human triage before being processed. label Dec 7, 2021
@b-enoit-be b-enoit-be mentioned this issue Dec 10, 2021
Merged
@ansibot ansibot added the has_pr This issue has an associated PR. label Dec 10, 2021
samccann pushed a commit that referenced this issue Dec 13, 2021
@b-enoit-be
Resolves #76449 Misplaced added version info (#76539)
8a562ea 
`.. versionadded::` are coming right after the section tittle, and was misplaced here
bcoca pushed a commit to bcoca/ansible that referenced this issue Dec 15, 2021
@b-enoit-be @bcoca
Resolves ansible#76449 Misplaced added version info (ansible#76539)
3568080 
`.. versionadded::` are coming right after the section tittle, and was misplaced here
@ansible ansible locked and limited conversation to collaborators Dec 27, 2021
konstruktoid pushed a commit to konstruktoid/ansible-upstream that referenced this issue Feb 2, 2022
@b-enoit-be @konstruktoid
Resolves ansible#76449 Misplaced added version info (ansible#76539)
4d93afd 
`.. versionadded::` are coming right after the section tittle, and was misplaced here
bcoca pushed a commit to bcoca/ansible that referenced this issue Feb 7, 2022
@b-enoit-be @bcoca
Resolves ansible#76449 Misplaced added version info (ansible#76539)
0712a12 
`.. versionadded::` are coming right after the section tittle, and was misplaced here
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
affects_2.13 docs This issue/PR relates to or includes documentation. has_pr This issue has an associated PR. support:core This issue/PR relates to code supported by the Ansible Engineering Team.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Resolves #76449 Misplaced added version info
3 participants
@mkrizek @ansibot @b-enoit-be