ci(quality-checks): introduce quality checks workflow

[tom-rm-meyer-ISST]

Description

This PR shall support the committers in ensuring the open-source policies by making use of the 1.3.x release guideline automation. For non-product repositories it can check for missing / incorrect notice sections.

I provided an initial configuration:

• exclude
  • all kits (except puris / scdn)
  • blog/
  • blog-changelog/
  • blog-meeting-minutes/

Currently excluded but to be discussed:

• docs/ includees release (TRG), oss, website-guidelines, tutorials, etc
• CONTRIBUTING.md

2026-08-13: Just reiterated it. Did plenty of additional stuff to ensure puris and scdn are fine (overshooted)

• license files in the past are fine (also in verisoned source url)
• fixed pipelines (markdown lint hitting source url bare url in markdown link)
• merged + covering the versions that came in between

Pre-review checks

Please ensure to do as many of the following checks as possible, before asking for committer review:

• DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
• Copyright and license header are present on all affected files

[tom-rm-meyer-ISST]

@stephanbcbauer this took me more time than I wanted now. I optimized nearly to the end and way to much.

A thing I noticed: source url is often missing and h2 note is often not fully uppercased. Maybe we want to allow Note too?

[stephanbcbauer]

@stephanbcbauer this took me more time than I wanted now. I optimized nearly to the end and way to much.

A thing I noticed: source url is often missing and h2 note is often not fully uppercased. Maybe we want to allow Note too?

Would work for me. How much effort would it be to allow it? We could restrict it later on :)

[Copilot]

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

[tom-rm-meyer-ISST]

@stephanbcbauer this took me more time than I wanted now. I optimized nearly to the end and way to much.
A thing I noticed: source url is often missing and h2 note is often not fully uppercased. Maybe we want to allow Note too?

Would work for me. How much effort would it be to allow it? We could restrict it later on :)

It's already restricted. Allowing it is around an hour for me and some time for you. We would need to update the tooling in https://github.com/eclipse-tractusx/sig-release and do releases of the tool and action / workflow. The pipeline uses the latest available action.

[stephanbcbauer]

Than let's do the no effort version :)