Avoid running tests when only docs are changed

[nrobinaubertin]

Overview

Avoid running tests when only docs are changed.

Checklist

• The charm style guide was applied
• The contributing guide was applied
• The changes are compliant with ISD054 - Managing Charm Complexity
• The documentation is generated using src-docs
• The documentation for charmhub is updated.
• The PR is tagged with appropriate label (urgent, trivial, complex)

[github-actions]

Test coverage for 68a812e

Name              Stmts   Miss Branch BrPart  Cover   Missing
-------------------------------------------------------------
src/charm.py        314     38     86     17    86%   129, 131, 140, 142, 150-151, 291->296, 466-467, 479-481, 486-487, 498-500, 505-506, 518-520, 525-526, 538-540, 566-568, 608->exit, 615-616, 618->exit, 624, 652-658, 684->exit, 698-699, 709->exit, 723
src/database.py      30      1      8      1    95%   56
-------------------------------------------------------------
TOTAL               344     39     94     18    87%

Static code analysis report

Run started:2023-11-29 02:21:49.588487

Test results:
  No issues identified.

Code scanned:
  Total lines of code: 1841
  Total lines skipped (#nosec): 1
  Total potential issues skipped due to specifically being disabled (e.g., #nosec BXXX): 0

Run metrics:
  Total issues (by severity):
  	Undefined: 0
  	Low: 0
  	Medium: 0
  	High: 0
  Total issues (by confidence):
  	Undefined: 0
  	Low: 0
  	Medium: 0
  	High: 0
Files skipped (0):

[yanksyoon]

Nice!

[jdkandersson]

I'm not sure this will work since we have required checks that must pass to be able to merge?

[arturo-seijas]

How does the publishing workflow work if there's no charm to publish? Will it skip the step or break?

[nrobinaubertin]

Responding to @jdkandersson and @arturo-seijas: I thought it would retain the status of the last CI. But it did launch it again so I put the PR into draft mode again. If I cannot confirm that:

• it will not relaunch the CI
• it uses the last status of the CI

I'll will not put it into ready again.

[arturo-seijas]

Responding to @jdkandersson and @arturo-seijas: I thought it would retain the status of the last CI. But it did launch it again so I put the PR into draft mode again. If I cannot confirm that:

• it will not relaunch the CI
• it uses the last status of the CI

I'll will not put it into ready again.

You'll probably need to skip charm publishing in the operator workflows if the charm file is not present. That would probably suffice. You'll still need to launch the workflow because publishing, if enabled, is done there

[nrobinaubertin]

I'm closing this as I have made no progress and the issue is complex enough that we need more discussions