feat: display juju debug-log in integration test runs

[PietroPasotti]

Change to _charm-quality-checks.yaml (integration tests part) adding two steps:

for each file found in ./.logs:

1. print to console
2. upload it as artifact

the idea is, we can put our juju debug-log output in there, and the CI will display them and upload as artifact.

Context: canonical/pytest-jubilant#11

Tandem PR to demonstrate the workflow in action: https://github.com/canonical/o11y-tester-operator/actions/runs/16414197049

[lucabello]

To re-review this PR, I would like:

• convert the PR title to conventional commits format, like we practice everywhere
• test the branch with some repository (if you don't know which one, use https://github.com/canonical/o11y-tester-operator) and link a successful run here
• consider updating the diagram here and see how it looks like (adding another box under integration tests maybe)?

[PietroPasotti]

@lucabello ready for another round, all points addressed

[lucabello]

@copilot please make comment suggestions that would make the workflows lint pass.

[Copilot]

@copilot please make comment suggestions that would make the workflows lint pass.

Fixed in 07b4840. The issue was a shellcheck SC2193 warning on the [[ "${{ inputs.log-path }}" = /* ]] comparison — actionlint replaces GitHub expressions with placeholders before passing to shellcheck, so shellcheck saw a literal string being compared to a glob pattern (/*) and flagged it as "can never be equal". Replaced it with a case statement which shellcheck handles correctly. actionlint now passes with no errors.

[Copilot]

Pull request overview

This PR extends the charm CI reusable workflows to surface integration test logs in GitHub Actions output and as downloadable artifacts, making debugging (e.g., Juju debug-log) easier across charm repositories.

Changes:

• Adds a new log-path workflow input (default .logs) to control where integration test logs are collected from.
• Updates the quality-checks workflow to display *.txt logs in the job output and upload the log directory as an artifact.
• Updates the README Mermaid workflow diagram to include the new log display/upload steps.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 9 comments.

File	Description
README.md	Documents the additional “Display logs” / “Upload logs” steps in the workflow diagram.
.github/workflows/charm-pull-request.yaml	Introduces log-path input and forwards it into the reusable quality-checks workflow.
.github/workflows/_charm-quality-checks.yaml	Adds log-path input and implements log display + upload behavior for integration runs.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.