* porting_guide_core_2.19.rst: add clatifications on the required non-string key conversion
* Update docs/docsite/rst/porting_guides/porting_guide_core_2.19.rst
Co-authored-by: Don Naro <dnaro@redhat.com>
* Update docs/docsite/rst/porting_guides/porting_guide_core_2.19.rst
Co-authored-by: Don Naro <dnaro@redhat.com>
* Add an example how to convert
* Add example
* Change example
* Update docs/docsite/rst/porting_guides/porting_guide_core_2.19.rst
Co-authored-by: Matt Clay <matt@mystile.com>
* Update docs/docsite/rst/porting_guides/porting_guide_core_2.19.rst
Co-authored-by: Matt Clay <matt@mystile.com>
* Update docs/docsite/rst/porting_guides/porting_guide_core_2.19.rst
Co-authored-by: Matt Clay <matt@mystile.com>
* Update docs/docsite/rst/porting_guides/porting_guide_core_2.19.rst
* Update docs/docsite/rst/porting_guides/porting_guide_core_2.19.rst
Co-authored-by: Matt Clay <matt@mystile.com>
---------
Co-authored-by: Don Naro <dnaro@redhat.com>
Co-authored-by: Matt Clay <matt@mystile.com>
* update core support matrix 2.19
* fix formatting and GA date
* Update docs/docsite/rst/reference_appendices/release_and_maintenance.rst
Co-authored-by: Matt Martz <matt@sivel.net>
* Update docs/docsite/rst/reference_appendices/release_and_maintenance.rst
Co-authored-by: Maxwell G <maxwell@gtmx.me>
* add reference to changelog
---------
Co-authored-by: Matt Martz <matt@sivel.net>
Co-authored-by: Maxwell G <maxwell@gtmx.me>
We should use the official action for retrieving the token to use for
the issue/PR triage and dependency update workflows instead of the one
we were using before.
This makes slight changes to the handling of universal lockfiles. These
were regenerated with `nox -e pip-compile -- --no-upgrade` to keep the
versions the same but adapt to the new way uv simplifies environment
markers.
The lockfiles for the pip-compile session itself were never updated
because I forgot to add them to the update workflow.
The pr_labeler lockfile is still excluded, but that's intentional for
now. I'd like this to happen manually or as part of a separate automated
workflow for now, as there's no automated tests for that script as of
yet, so I don't want it to randomly break when we merge these general
pip-compile-dev PRs.
Previously, this only would create a PR when the branch was newly
created earlier in the workflow (assuming that branches would be deleted
once the previous dependency update PR was merged), but it was possible
for the branch to already exist but not have a PR open against it.
This uses the Github API to properly check whether a PR already exists.
* Add yamllint check for RST code listings.
* Address review comments.
* Sort languages and remove no longer needed duplicates.
* Enable warnings, but disable all failing rules.
* Improve formulation.
Co-authored-by: Don Naro <dnaro@redhat.com>
* Show allowed languages when no or invalid language is supplied. Improve line lengths.
* Make sure that 'yamllint .' passes.
* Fix indentation issues introduced in #2095.
---------
Co-authored-by: Don Naro <dnaro@redhat.com>
* fix broken links
* fix some more label problems
* Apply suggestions from code review
Co-authored-by: Felix Fontein <felix@fontein.de>
---------
Co-authored-by: Felix Fontein <felix@fontein.de>
* union documented incorrectly
The invalid documentation of union was fixed in https://github.com/ansible/ansible/issues/82199 but didn't populate into this section of the docs.
* Apply suggestions from code review
Co-authored-by: Felix Fontein <felix@fontein.de>
---------
Co-authored-by: Felix Fontein <felix@fontein.de>
* Update playbooks_error_handling.rst
Add example for using own variables in conditions
* Apply suggestions from code review
Co-authored-by: Don Naro <dnaro@redhat.com>
---------
Co-authored-by: Sandra McCann <samccann@redhat.com>
Co-authored-by: Don Naro <dnaro@redhat.com>
