[TASK] Identify and remove obsolete workflows

[RamakrishnanPK]

Fixes #218

[AlexanderLanin]

@RamakrishnanPK there is a conflict unfortunately which only you can resolve since its a protected branch

[pawelrutkaq]

@PiotrKorkus

[pawelrutkaq]

did we submit prs to all consumers off thos workflows in score that are not pinned to stable sha?

[AlexanderLanin]

Yeah, months ago

[MaximilianSoerenPollak]

I am not quiet sure where you found that these workflows are obsolete.
They are still being used by repositories.

The template-sync one and the score-pr-checks might be able to be deleted but require further questioning to infrastructure slack channel or mcp_server maintainers.

---

Edit:

I just saw the issue that this is suppose to fix.
So then this vital piece of information is missing here as well. Is the old check covered by the new on-pr and if so with what mechanism?
Cause if we now for example force repos to have pre-commit I'm unsure if this will be very popular or accepted and they most likely will want to hold on to the old ones.

[AlexanderLanin]

@MaximilianSoerenPollak any updates?

[AlexanderLanin]

Current Eclipse SCORE @main consumers

Current reusable-workflow references to eclipse-score/cicd-workflows/...@main on the repositories’ default branches:

Repository	Current @main workflow references	Pinning PR
logging	bzlmod-lock-check.yml, copyright.yml, docs-cleanup.yml, format.yml, daily.yml, license-check.yml, qnx-build.yml	#302 (all except qnx-build.yml)

The PR pins the listed reusable-workflow references to commit 37eaadadfefc263d94a858d25665735659e916fa.

[AlexanderLanin]

@RamakrishnanPK can you resolve merge conflicts please, I think we are ready