ci: ansible-lint - remove .collection directory from converted collection [citest_skip]

[richm]

The new ansible-lint@v26 does not like it when there is a .collection directory
with a galaxy.yml in the converted collection, so remove it, since it is not
needed for ansible-lint.

Signed-off-by: Rich Megginson rmeggins@redhat.com

Summary by Sourcery

CI:

• Extend the ansible-lint workflow cleanup step to also delete the converted collection's .collection directory.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the ansible-lint GitHub Actions workflow to additionally remove the temporary .collection directory from the converted collection before running ansible-lint, aligning with ansible-lint v26 expectations.

Flow diagram for updated cleanup in ansible-lint workflow

flowchart TD
  A[Start ansible-lint job] --> B[Run tox with TOXENV=collection]
  B --> C[Set coll_dir to .tox/ansible_collections/namespace/name]
  C --> D[Cleanup converted collection]
  D --> D1[Remove coll_dir/.ansible]
  D --> D2[Remove .tox/ansible-plugin-scan]
  D --> D3[Remove coll_dir/.collection]
  D1 --> E[Ensure coll_dir/.git exists]
  D2 --> E
  D3 --> E
  E[Create coll_dir/.git directory] --> F[Run ansible-lint action]
  F --> G[End job]

Loading

File-Level Changes

Change	Details	Files
Extend the cleanup step in the ansible-lint CI workflow to delete the converted collection’s .collection directory.	Update the cleanup rm -rf command in the ansible-lint job to include the $coll_dir/.collection path alongside existing artifacts .collection is removed after collection conversion and before ansible-lint is invoked to avoid conflicts with ansible-lint v26 behavior	.github/workflows/ansible-lint.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}