Karsten Hassel 1998b6273b testing: update "Enforce Pull-Request Rules" workflow (#3987) ...

With this update the workflow file from inside the feature branch is
used, not the old stuff coming from `master` as before. This does not
help for the currently failing job which still comes from `master` (we
have to live with this until next release), but this will help in the
future to prevent such errors.

Tested this on my fork:
- base against `develop`: workflow is skipped
- base against `master`: workflow fails
- base against `master` with label `mastermerge`: workflow is skipped

I took this new workflow from the same repo where the previous workflows
was taken (see diff for the link) so this is the further development.

2025-12-10 22:28:34 +01:00

..

automated-tests.yaml

[chore] update dependencies and min. node version (#3986)

2025-12-10 19:42:20 +01:00

dep-review.yaml

Bump actions/checkout from 5 to 6 (#3972)

2025-11-24 13:07:52 +01:00

electron-rebuild.yaml

[chore] update dependencies and min. node version (#3986)

2025-12-10 19:42:20 +01:00

enforce-pullrequest-rules.yaml

testing: update "Enforce Pull-Request Rules" workflow (#3987)

2025-12-10 22:28:34 +01:00

release-notes.yaml

[core] auto create release notes with every push on develop (#3985)

2025-12-10 11:56:31 -06:00

spellcheck.yaml

Bump actions/checkout from 5 to 6 (#3972)

2025-11-24 13:07:52 +01:00

stale.yaml

Bump github actions and dependencies (#3882)

2025-09-08 14:29:06 +02:00