Replace "fixes" by "closes"

[koppor]

Multiple contributors did not use "fixes", but other words (not recognized by GitHub https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue)

The explanation seems to be that "fixes" is interpreted as fixing a bug only. Thus, they changed the wording. See koppor#540 (comment) for that explanation.

"Resolves" has more weight to me than "Closes". However, GitHub has "Close" at issues, therefore, I propose to use "Closes" as text.

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.

[k3KAW8Pnf7mkmdSMPHz27]

I really dislike "Closes" but I agree with the logic.

[k3KAW8Pnf7mkmdSMPHz27]

Wait a sec.

[k3KAW8Pnf7mkmdSMPHz27]

I think the editor helpfully added something there for me, my bad for not double checking

[Siedlerchr]

I prefer fixes as well, but closes is fine for me ... And I will continue to use FIxes

[k3KAW8Pnf7mkmdSMPHz27]

I prefer fixes as well, but closes is fine for me ... And I will continue to use FIxes

I'll be contrarian and start using Resolves 😎

Some are better for different contexts, and I think Closes might just be the weirdest except for the reference to the GitHub UI.

[Siedlerchr]

I prefer fixes as well, but closes is fine for me ... And I will continue to use FIxes

I'll be contrarian and start using Resolves 😎

Some are better for different contexts, and I think Closes might just be the weirdest except for the reference to the GitHub UI.

+1 for resolves!

[github-actions]

The build for this PR is no longer available. Please visit https://builds.jabref.org/main/ for the latest build.