Do not run CI on documentation changes

[ann0see]

Short description of changes
Stops running the CI if the documentation changes. There is no need of running the CI on non source files. New version of #1921 I think this is a quick fix (and can be update ofc.)

CHANGELOG: Stop running Autobuild if only documentation is updated to avoid wasting computation time.

Context: Fixes an issue?
No. Related to #2282 (comment)

Does this change need documentation? What needs to be documented and how?
No

Status of this Pull Request
Ready for review

What is missing until this pull request can be merged?

Checklist

• I've verified that this Pull Request follows the general code principles
• I tested my code and it does what I want (https://github.com/ann0see/jamulus/actions/runs/2013115499 and https://github.com/ann0see/jamulus/commits/autobuild/noRunDocs are small tests)
• My code follows the style guide
• I waited some time after this Pull Request was opened and all GitHub checks completed without errors.
• I've filled all the content above

[ann0see]

Peter‘s alternative approach might also work, but this is faster to implement.

[hoffie]

Seems safe to do.

Note: README.md is part of Jamulus.pro's DISTFILES, so I guess it's part of make dist, but we don't run that on CI.

paths-ignore doesn't work for tags per the docs, so even if we ignore too much, we should be on the safe side for releases.

The duplication is not nice, but I don't see a way around.
Doing trigger-based ignores has the advantage of being able to still run the Action manually if this logic is wrong for some reason.

[hoffie]

Maybe I'm the only one caring about git log cleanliness, but I'd prefer context in the commit message.
Autobuild: Don't run on README/docs-only commits (the current message isn't clear that it's about the auto build logic)

[softins]

Just wondering, what about ChangeLog? And are the other *.md files in the root dir going to move into docs/ at some point?

[ann0see]

Hmm. I've now added other files (except for the ChangeLog since it's somehow related to the release process)

[pljones]

Just wondering, what about ChangeLog? And are the other *.md files in the root dir going to move into docs/ at some point?

ChangeLog, README.md and any licence-related files should stay at root level, otherwise discovery proves more difficult. (Particularly auto-discovery.)

[ann0see]

Probably true 😀. Not sure what the gold standard is.

[softins]

Just wondering, what about ChangeLog? And are the other *.md files in the root dir going to move into docs/ at some point?

ChangeLog, README.md and any licence-related files should stay at root level, otherwise discovery proves more difficult. (Particularly auto-discovery.)

Sorry, I conflated two things in my comment:

• should ChangeLog be included in the files that do not trigger a rebuild?
• should the other *.md files except README.md be moved into docs/?

[pljones]

I think all the remaining top-level docs need to stay there.

• APPLEAPPSTORE.LICENCE.WAIVER and COPYING are licence-related
• README.md is definitely needed there
• Anyone looking for COMPILING.md shouldn't have to look to far - it's a "first place of reference" for those who are doing it themselves
• SECURITY.md and CONTRIBUTING.md could perhaps move unless used by Github for "project completeness scoring" or whatever
• Jamulus.entitlements - no idea what this is or why it's at top level.

[ann0see]

should ChangeLog be included in the files that do not trigger a rebuild?

I excluded it for the reason that I think the Debian build uses it and it’s related to the release process

[ann0see]

Jamulus.entitlements - no idea what this is or why it's at top level.

#2529