(Test) commit submodules

[subhramit]

To test #12752

Mandatory checks

• I own the copyright of the code submitted and I licence it under the MIT license
• Change in CHANGELOG.md described in a way that is understandable for the average user (if change is visible to the user)
• Tests created for changes (if applicable)
• Manually tested changed features in running JabRef (always required)
• Screenshots added in PR description (if change is visible to the user)
• 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.

[subhramit]

@koppor false positive? https://github.com/JabRef/jabref/actions/runs/13887489384/job/38854160250?pr=12755

[koppor]

@koppor false positive? JabRef/jabref/actions/runs/13887489384/job/38854160250?pr=12755

I think, I mixed up again pull_request ( contributor branch with all changes, but not with full token rights) and pull_request_target (main branch with full token rights). Check is now done at pull_request - fa74258

[koppor]

Still not working. Need to check.

[subhramit]

@koppor it seems to me like we are triggering the error when NO submodule changes are detected (! in front)

[koppor]

@koppor it seems to me like we are triggering the error when NO submodule changes are detected (! in front)

The -vz in grep reverses the grep change

[subhramit]

Woohoo done

[Siedlerchr]

I guess this test PR is now obsolete

[subhramit]

I guess this test PR is now obsolete

Let me try out once - as it was not working last time

[subhramit]

Job was skipped, olly probably disabled the test
Closing for now till needed

[trag-bot]

@trag-bot didn't find any issues in the code! ✅✨

[jabref-machine]

Hey, we noticed that you force-pushed your changes. Force pushing is a bad practice when working together on a project (mainly because it is not supported well by GitHub itself). Commits are lost and comments on commits lose their context, thus making it harder to review changes. At the end, all commits will be squashed anyway before being merged into the main branch.

In future, please avoid that. For now, you can continue working.