We had the issue that the deployment workflow as not triggered for some PRs. See #9769 (comment).

The reason was a wrong trigger. We had the idea that binaries should only be created if there actually was changed something leading to changes in the binaries. Only changing tests does not lead to a change in the binary. For instance, test-only PRs do not change the binary. -- GitHub's branch protection rules demand that the workflows run. Regardless if the trigger ignores the changes. Thus, either make the workflows success optional - or trigger the workflow always.

Since test-only PRs are very seldom and we do want to have the deplyoment required, I remove the "filter" at the trigger.

Kind of hotfix.

Mandatory checks

• Change in CHANGELOG.md described in a way that is understandable for the average user (if applicable)
• Tests created for changes (if applicable)
• Manually tested changed features in running JabRef (always required)
• Screenshots added in PR description (for UI changes)
• Checked developer's documentation: Is the information available and up to date? If not, I outlined it in this pull request.
• Checked documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request to the documentation repository.