From 4032f6c0816a7440867f9a8a0f1b5eb3f1d6cf6e Mon Sep 17 00:00:00 2001 From: Abhijeet Kasurde Date: Wed, 27 Aug 2025 14:49:54 -0700 Subject: [PATCH 1/2] Add a recommendation for using reserved tags * Special tags like 'tagged', 'untagged' and 'all' should not be assign as tags and should be treated as special ones. Update the documentation about the same. Signed-off-by: Abhijeet Kasurde --- docs/docsite/rst/playbook_guide/playbooks_tags.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/playbook_guide/playbooks_tags.rst b/docs/docsite/rst/playbook_guide/playbooks_tags.rst index c4611d1c697..e1d5818cba1 100644 --- a/docs/docsite/rst/playbook_guide/playbooks_tags.rst +++ b/docs/docsite/rst/playbook_guide/playbooks_tags.rst @@ -320,7 +320,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. - +These keywords are designed to filter tasks based on their tagging status so it is recommended not to assign them as specific tag names. Always and Never ---------------- From 7e565112fee889824ed22cc841736836ab5a53d1 Mon Sep 17 00:00:00 2001 From: Abhijeet Kasurde Date: Thu, 28 Aug 2025 10:20:02 -0700 Subject: [PATCH 2/2] Review requests Signed-off-by: Abhijeet Kasurde --- docs/docsite/rst/playbook_guide/playbooks_tags.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/docsite/rst/playbook_guide/playbooks_tags.rst b/docs/docsite/rst/playbook_guide/playbooks_tags.rst index e1d5818cba1..3196aefafcf 100644 --- a/docs/docsite/rst/playbook_guide/playbooks_tags.rst +++ b/docs/docsite/rst/playbook_guide/playbooks_tags.rst @@ -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. -These keywords are designed to filter tasks based on their tagging status so it is recommended not to assign them as specific tag names. +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 ----------------