Skip to content

add the commit_changes role #686

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.

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 1 commit into
base: main
Choose a base branch
from
Open

add the commit_changes role #686

wants to merge 1 commit into from

Conversation

fredericlepied
Copy link
Contributor

@fredericlepied fredericlepied commented May 22, 2025

SUMMARY
ISSUE TYPE
  • New role
Tests

Test-Hint: no-check

@fredericlepied fredericlepied requested review from a team as code owners May 22, 2025 13:43
@dcibot
Copy link
Collaborator

dcibot commented May 22, 2025

from change #686:

  • no check (not a code change)

1 similar comment
@dcibot
Copy link
Collaborator

dcibot commented May 22, 2025

from change #686:

  • no check (not a code change)

Copy link
Contributor

coderabbitai bot commented May 22, 2025

📝 Walkthrough

Walkthrough

A new Ansible role, commit_changes, was introduced to automate staging and committing changes in a Git repository. Documentation and integration tests for this role were added. Version numbers in spec and metadata files were incremented, and the README was updated to reference the new role.

Changes

Files/Paths Change Summary
README.md Added entry for the new redhatci.ocp.commit_changes role in the Roles section.
roles/commit_changes/README.md New documentation file describing the commit_changes role and its input variables.
roles/commit_changes/tasks/main.yml New Ansible task file implementing variable checks, Git author config, staging, and committing changes.
tests/integration/targets/commit_changes/commit_changes.yml,
.../runme.sh
Added integration test playbook and shell script to test the new role.
ansible-collection-redhatci-ocp.spec Bumped version from 2.6.EPOCH to 2.7.EPOCH and added changelog for the new role.
galaxy.yml Updated version to 2.7.0 and added comments to keep it in sync with the spec file.

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d14dbe4 and 8e94822.

📒 Files selected for processing (7)
  • README.md (1 hunks)
  • ansible-collection-redhatci-ocp.spec (2 hunks)
  • galaxy.yml (1 hunks)
  • roles/commit_changes/README.md (1 hunks)
  • roles/commit_changes/tasks/main.yml (1 hunks)
  • tests/integration/targets/commit_changes/commit_changes.yml (1 hunks)
  • tests/integration/targets/commit_changes/runme.sh (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • galaxy.yml
  • ansible-collection-redhatci-ocp.spec
🚧 Files skipped from review as they are similar to previous changes (5)
  • README.md
  • tests/integration/targets/commit_changes/runme.sh
  • roles/commit_changes/README.md
  • tests/integration/targets/commit_changes/commit_changes.yml
  • roles/commit_changes/tasks/main.yml
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: Sanity Check (stable-2.18)
  • GitHub Check: Sanity Check (stable-2.9)
  • GitHub Check: Ansible-lint Check
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

Merge Failed.

This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset.
Warning:
Error merging github.com/redhatci/ansible-collection-redhatci-ocp for 686,030e2ad5a4572b816added62b831aeff82d6aa19

@fredericlepied fredericlepied marked this pull request as draft May 22, 2025 13:44
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🔭 Outside diff range comments (1)
roles/commit_changes/tasks/main.yml (1)

30-37: 🛠️ Refactor suggestion

Avoid shell‐splitting issues by using list/argv form.
Passing the commit message as a single argument prevents injection and ensures messages with spaces work:

- name: Commit changes
  ansible.builtin.command:
    argv:
      - git
      - commit
      - -m
      - "{{ commit_message }}"
  args:
    chdir: "{{ commit_directory }}"
  register: commit_result
  failed_when: commit_result.rc > 1
  changed_when: commit_result.rc == 0
🧹 Nitpick comments (7)
tests/integration/inventory (1)

2-2: Avoid hardcoding local paths in inventory
The ansible_python_interpreter is pointed at a user-specific venv path. For portability, consider using a generic interpreter (e.g. /usr/bin/env python3) or parameterizing via an environment variable or inventory var.

roles/commit_changes/defaults/main.yml (1)

1-4: Add newline at end of file
YAML lint flagged a missing newline at EOF. Please ensure there’s a trailing newline to comply with common YAML style guidelines.

🧰 Tools
🪛 YAMLlint (1.37.1)

[error] 4-4: no new line character at the end of file

(new-line-at-end-of-file)

tests/integration/integration_config.yml (1)

1-7: Ensure trailing newline for YAML file
Add a newline at the end of this file to satisfy YAML style checks and avoid “no new line at end of file” warnings.

tests/integration/targets/commit_changes/commit_changes.yml (1)

1-7: Optimize playbook for speed
Since this integration test doesn’t need facts, you could add gather_facts: no under the play to reduce runtime.

roles/commit_changes/README.md (1)

1-3: Unify Markdown heading style.
Currently the top-level header uses Setext while the others use ATX, which triggers MD003. For consistency, convert to ATX:

- commit_changes
- ===============
+ # commit_changes
roles/commit_changes/tasks/main.yml (1)

1-7: Add a check that the directory is a Git repo.
Right now we only assert the variables exist. It’s safer to verify that commit_directory/.git actually exists before proceeding:

- name: Check for Git repository
  ansible.builtin.stat:
    path: "{{ commit_directory }}/.git"
  register: git_dir

- name: Fail if not a Git repository
  ansible.builtin.assert:
    that:
      - git_dir.exists
    fail_msg: "Directory {{ commit_directory }} is not a Git repository"
tests/integration/targets/commit_changes/tasks/main.yml (1)

3-7: Ensure directory removal is recursive if needed.
To guarantee cleanup of non-empty dirs, add recurse: yes:

- name: Cleanup target directory
  ansible.builtin.file:
    path: "{{ commit_directory }}"
    state: absent
    recurse: yes
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b938589 and 030e2ad.

📒 Files selected for processing (9)
  • README.md (1 hunks)
  • roles/commit_changes/README.md (1 hunks)
  • roles/commit_changes/defaults/main.yml (1 hunks)
  • roles/commit_changes/tasks/main.yml (1 hunks)
  • tests/integration/integration_config.yml (1 hunks)
  • tests/integration/inventory (1 hunks)
  • tests/integration/targets/commit_changes/commit_changes.yml (1 hunks)
  • tests/integration/targets/commit_changes/runme.sh (1 hunks)
  • tests/integration/targets/commit_changes/tasks/main.yml (1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.37.1)
roles/commit_changes/defaults/main.yml

[error] 4-4: no new line character at the end of file

(new-line-at-end-of-file)

🪛 markdownlint-cli2 (0.17.2)
roles/commit_changes/README.md

6-6: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)


15-15: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)


19-19: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

🔇 Additional comments (5)
README.md (1)

50-50: Role entry added correctly
The commit_changes role is listed in the Roles table with an accurate link and description. Positioning and formatting match existing entries.

roles/commit_changes/README.md (3)

6-14: Variables section is clear and accurate.
The table correctly documents required and optional inputs.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

6-6: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)


15-18: Dependencies section is correct.
No external requirements—documentation matches implementation.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

15-15: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)


19-21: License section is appropriate.
GNU GPLv3 is properly declared.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

19-19: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

roles/commit_changes/tasks/main.yml (1)

25-29: Staging changes looks good.
Using git add --all . with chdir correctly stages all file states.

Comment on lines 3 to 6
dir=$(dirname "$0")

exec ansible-playbook -i $dir/../../inventory -e @$dir/../../integration_config.yml commit_changes.yml

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Ensure playbook path and variables are quoted and correctly referenced.
The script determines its own directory but then runs commit_changes.yml relative to the current working directory, which may cause “file not found” errors if you invoke the script from elsewhere. Also, the inventory and vars paths should be quoted to handle spaces.
Apply this diff:

- dir=$(dirname "$0")
- 
- exec ansible-playbook -i $dir/../../inventory -e @$dir/../../integration_config.yml commit_changes.yml
+ dir="$(dirname "$0")"
+
+ # run from the role’s test directory
+ cd "$dir"
+
+ exec ansible-playbook \
+   "$dir/commit_changes.yml" \
+   -i "$dir/../../inventory" \
+   -e "@$dir/../../integration_config.yml"
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
dir=$(dirname "$0")
exec ansible-playbook -i $dir/../../inventory -e @$dir/../../integration_config.yml commit_changes.yml
dir="$(dirname "$0")"
# run from the role’s test directory
cd "$dir"
exec ansible-playbook \
"$dir/commit_changes.yml" \
-i "$dir/../../inventory" \
-e "@$dir/../../integration_config.yml"
🤖 Prompt for AI Agents
In tests/integration/targets/commit_changes/runme.sh around lines 3 to 6, the
ansible-playbook command uses unquoted paths and references the playbook
relative to the current directory instead of the script directory. To fix this,
quote all path variables to handle spaces and reference commit_changes.yml using
the script directory variable to ensure the correct file is found regardless of
the current working directory.

Comment on lines 9 to 19
- name: Set git author name
ansible.builtin.command: git config user.name "{{ commit_author_name }}"
args:
chdir: "{{ commit_directory }}"
when:
- commit_author_name is defined
- commit_author_name | length > 0
Copy link
Contributor

@coderabbitai coderabbitai bot May 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Use the idempotent git_config module for author settings.
Replacing raw git config commands with ansible.builtin.git_config improves idempotency and readability:

- name: Set git author name
  ansible.builtin.git_config:
    name: user.name
    value: "{{ commit_author_name }}"
    scope: local
    repo: "{{ commit_directory }}"
  when:
    - commit_author_name is defined
    - commit_author_name | length > 0

- name: Set git author email
  ansible.builtin.git_config:
    name: user.email
    value: "{{ commit_author_email }}"
    scope: local
    repo: "{{ commit_directory }}"
  when:
    - commit_author_email is defined
    - commit_author_email | length > 0

Also applies to: 17-23

🤖 Prompt for AI Agents
In roles/commit_changes/tasks/main.yml lines 9 to 15 and also lines 17 to 23,
replace the ansible.builtin.command tasks that run raw git config commands with
the ansible.builtin.git_config module. Use the git_config module's parameters:
name for the config key (user.name or user.email), value for the corresponding
variable, scope set to local, and repo set to commit_directory. Keep the
existing when conditions to check if the variables are defined and non-empty.
This change ensures idempotency and improves readability.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, good idea.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fredericlepied, great to hear you're on board with using the git_config module! It'll definitely make the role more robust and easier to maintain. 🐰

(ノ◕ヮ◕)ノ*:・゚✧ ♪~(´ε` )


If you found this review helpful, would you consider giving us a shout-out on X?

Thank you for using CodeRabbit!

Comment on lines 52 to 67
- name: Verify that commit was made
ansible.builtin.assert:
that:
- commit_result.changed

- name: Verify commit message is correct
ansible.builtin.command: git log -1 --pretty=%B
args:
chdir: "{{ commit_directory }}"
register: git_log

- name: Assert git log message matches commit_message
ansible.builtin.assert:
that:
- git_log.stdout.strip() == commit_message

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Expand tests to cover author overrides.
We verify that a commit is made and the message matches, but we don’t assert commit_author_name/email behavior. Consider adding:

- name: Get latest commit author name
  ansible.builtin.command:
    argv:
      - git
      - log
      - -1
      - --pretty=%an
  args:
    chdir: "{{ commit_directory }}"
  register: git_author

- name: Assert commit author name
  ansible.builtin.assert:
    that:
      - git_author.stdout.strip() == commit_author_name
  when: commit_author_name is defined

Place these after the message assertion to fully cover optional author overrides.

🤖 Prompt for AI Agents
In tests/integration/targets/commit_changes/tasks/main.yml around lines 52 to
67, the current tests verify commit creation and message correctness but do not
check commit author name or email overrides. Add tasks after the commit message
assertion to run a git command retrieving the latest commit author name,
register its output, and assert that it matches the expected commit_author_name
variable. Include a conditional to run this assertion only if commit_author_name
is defined, ensuring coverage of optional author overrides.

@dcibot
Copy link
Collaborator

dcibot commented May 22, 2025

from change #686:

  • no check (not a code change)

1 similar comment
@dcibot
Copy link
Collaborator

dcibot commented May 22, 2025

from change #686:

  • no check (not a code change)

Copy link

Merge Failed.

This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset.
Warning:
Error merging github.com/redhatci/ansible-collection-redhatci-ocp for 686,f4c030e0d882f5f1536221488b5bb477c8481696

@dcibot
Copy link
Collaborator

dcibot commented May 22, 2025

from change #686:

  • no check (not a code change)

1 similar comment
@dcibot
Copy link
Collaborator

dcibot commented May 22, 2025

from change #686:

  • no check (not a code change)

Copy link

Merge Failed.

This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset.
Warning:
Error merging github.com/redhatci/ansible-collection-redhatci-ocp for 686,b429acfaa2dd5f047a0ba13af03eee2c711326b4

@dcibot
Copy link
Collaborator

dcibot commented May 26, 2025

from change #686:

  • no check (not a code change)

1 similar comment
@dcibot
Copy link
Collaborator

dcibot commented May 26, 2025

from change #686:

  • no check (not a code change)

Copy link

Merge Failed.

This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset.
Warning:
Error merging github.com/redhatci/ansible-collection-redhatci-ocp for 676,61963101253f7475b81c246cab8f9a66d4ef2d46

@dcibot
Copy link
Collaborator

dcibot commented May 26, 2025

from change #686:

  • no check (not a code change)

1 similar comment
@dcibot
Copy link
Collaborator

dcibot commented May 26, 2025

from change #686:

  • no check (not a code change)

Copy link

Merge Failed.

This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset.
Warning:
Error merging github.com/redhatci/ansible-collection-redhatci-ocp for 676,61963101253f7475b81c246cab8f9a66d4ef2d46

@dcibot
Copy link
Collaborator

dcibot commented May 26, 2025

from change #686:

  • no check (not a code change)

Copy link

Merge Failed.

This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset.
Warning:
Error merging github.com/redhatci/ansible-collection-redhatci-ocp for 676,61963101253f7475b81c246cab8f9a66d4ef2d46

@dcibot
Copy link
Collaborator

dcibot commented May 26, 2025

from change #686:

  • no check (not a code change)

Copy link
Contributor

@ramperher ramperher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to know a little bit about this: what's the main purpose of this role? Is it required for any of our CI integrations?

@fredericlepied
Copy link
Contributor Author

recheck

@dcibot
Copy link
Collaborator

dcibot commented Jun 3, 2025

from change #686:

  • no check (not a code change)

1 similar comment
@dcibot
Copy link
Collaborator

dcibot commented Jun 3, 2025

from change #686:

  • no check (not a code change)

Copy link

@dcibot
Copy link
Collaborator

dcibot commented Jun 5, 2025

from change #686:

  • no check (not a code change)

1 similar comment
@dcibot
Copy link
Collaborator

dcibot commented Jun 5, 2025

from change #686:

  • no check (not a code change)

Copy link

@dcibot
Copy link
Collaborator

dcibot commented Jun 5, 2025

from change #686:

  • no check (not a code change)

1 similar comment
@dcibot
Copy link
Collaborator

dcibot commented Jun 5, 2025

from change #686:

  • no check (not a code change)

Copy link

@dcibot
Copy link
Collaborator

dcibot commented Jun 6, 2025

from change #686:

  • no check (not a code change)

1 similar comment
@dcibot
Copy link
Collaborator

dcibot commented Jun 6, 2025

from change #686:

  • no check (not a code change)

Copy link

@dcibot
Copy link
Collaborator

dcibot commented Jun 6, 2025

from change #686:

  • no check (not a code change)

1 similar comment
@dcibot
Copy link
Collaborator

dcibot commented Jun 6, 2025

from change #686:

  • no check (not a code change)

Copy link

@fredericlepied fredericlepied marked this pull request as ready for review June 6, 2025 13:15
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (2)
roles/commit_changes/README.md (2)

1-4: Add a Requirements section.

The README jumps directly into the role description without listing prerequisites. Introduce a Requirements heading to note that Git CLI must be installed and available in PATH.


7-13: Expand variable docs with types, defaults, and an example.

The table omits data types and explicit defaults (null/None) for required parameters. Consider adding a Type column and default values, plus an Example snippet showing how to call the role with all required vars.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 030e2ad and d14dbe4.

📒 Files selected for processing (7)
  • README.md (1 hunks)
  • ansible-collection-redhatci-ocp.spec (2 hunks)
  • galaxy.yml (1 hunks)
  • roles/commit_changes/README.md (1 hunks)
  • roles/commit_changes/tasks/main.yml (1 hunks)
  • tests/integration/targets/commit_changes/commit_changes.yml (1 hunks)
  • tests/integration/targets/commit_changes/runme.sh (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • ansible-collection-redhatci-ocp.spec
  • galaxy.yml
🚧 Files skipped from review as they are similar to previous changes (3)
  • tests/integration/targets/commit_changes/runme.sh
  • README.md
  • roles/commit_changes/tasks/main.yml

Comment on lines +54 to +62
- name: Run the role under test
import_role:
name: redhatci.ocp.commit_changes

- name: Verify that commit was made
ansible.builtin.assert:
that:
- _cc_result.changed

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Capture the role’s result before asserting.

You’re importing the role without registering its output, so _cc_result will be undefined. Change to:

- name: Run the role under test
  include_role:
    name: redhatci.ocp.commit_changes
  register: _cc_result

This ensures you can assert on _cc_result.changed.

🤖 Prompt for AI Agents
In tests/integration/targets/commit_changes/commit_changes.yml around lines 54
to 62, the role is imported without capturing its result, so the variable
_cc_result is undefined when asserting. Replace the import_role task with
include_role and register its output to _cc_result. This allows the subsequent
assertion to correctly check if the role made changes by referencing
_cc_result.changed.

Comment on lines +69 to +73
- name: Assert git log message matches cc_message
ansible.builtin.assert:
that:
- git_log.stdout.strip() == cc_message

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Use a Jinja2 filter instead of .strip().

Ansible’s Jinja2 may not allow direct Python method calls. Replace:

- git_log.stdout.strip() == cc_message

with:

- git_log.stdout | trim == cc_message
🤖 Prompt for AI Agents
In tests/integration/targets/commit_changes/commit_changes.yml around lines 69
to 73, replace the Python string method call git_log.stdout.strip() with the
Jinja2 filter git_log.stdout | trim to ensure compatibility with Ansible's
templating engine. Update the assertion to use the Jinja2 trim filter for
stripping whitespace instead of the .strip() method.

Copy link

github-actions bot commented Jul 7, 2025

This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the Stale label Jul 7, 2025
@dcibot
Copy link
Collaborator

dcibot commented Jul 7, 2025

from change #686:

  • no check (not a code change)

1 similar comment
@dcibot
Copy link
Collaborator

dcibot commented Jul 7, 2025

from change #686:

  • no check (not a code change)

Copy link

@github-actions github-actions bot removed the Stale label Jul 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants