🐛 bug: git diff output in run-tests workflow is not documented or captured

[ashleyshaw]

What happened?

In the run-tests workflow, the git diff output is generated but not documented, captured, or used by subsequent workflow steps. This leads to ambiguity about whether the diff is for logging, debugging, or further use.

What did you expect to happen?

The purpose of the git diff output should be clearly documented. If the diff is intended to be consumed by subsequent steps, it should be saved to a file or exposed as a workflow output.

How can we reproduce this bug?

1. Trigger the run-tests workflow in the repository.
2. Observe the workflow step(s) where git diff is output.
3. Note that the output is displayed but not referenced or captured in later steps.

Relevant files, URLs, or code snippets

• PR: https://github.com/lightspeedwp/scripts/pull/22/files/c2ac8cc788ad8702cd1d9e889fe7dfc551586f2d
• Workflow: .github/workflows/run-tests.yml

Additional context

This issue was raised during review of PR #22. Clarifying and documenting the handling of the git diff output will improve maintainability and reduce confusion for contributors. Please refer to the LightSpeed Coding Standards and Workflow Documentation.

Environment

• Repository: lightspeedwp/scripts
• Workflow: run-tests

Labels

• github-workflow
• area:documentation
• enhancement
• status:needs-triage