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

..

ISSUE_TEMPLATE

Release 2.32.0 (#3826)

2025-07-01 00:10:47 +02:00

workflows

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

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

CODE_OF_CONDUCT.md

Add Code of Conduct (#3763)

2025-05-16 08:03:43 +02:00

CONTRIBUTING.md

[tests] migrate from jest to vitest (#3940)

2025-11-03 19:47:01 +01:00

dependabot.yaml

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

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

FUNDING.yaml

Use .yaml instead of .yml

2022-06-06 23:57:52 +02:00

header.png

Remove background.

2016-04-11 15:01:01 +02:00

PULL_REQUEST_TEMPLATE.md

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

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