Skip to content

Add a recommendation for using reserved tags #3012

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

Open
wants to merge 2 commits into
base: devel
Choose a base branch
from
Open

Add a recommendation for using reserved tags #3012

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4032f6c
Add a recommendation for using reserved tags
Akasurde Aug 27, 2025
7e56511
Review requests
Akasurde Aug 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions docs/docsite/rst/playbook_guide/playbooks_tags.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -319,8 +319,7 @@ Special tags
============

Ansible reserves several tag names for special behavior: ``always``, ``never``, ``tagged``, ``untagged`` and ``all``.
Both ``always`` and ``never`` are mostly for use in tagging the tasks themselves, the other three are used when selecting which tags to run or skip.

Both ``always`` and ``never`` are for use in tagging the tasks themselves, the other three should only be used as selection tags when choosing what to run or skip and not on the tasks themselves as that will lead to counterintuitive results.

Always and Never
----------------
Expand Down