CSL DOI test

[subhramit]

Closes _____
Describe the changes you have made here: what, where, why, ...
If your work is not yet complete, please open a draft pull request. In that case, outline your intended next steps. Do you need feedback? Will you continue in parallel? ...

Mandatory checks

• I own the copyright of the code submitted and I license 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]

Dumb me.

[Siedlerchr]

I would merge the tests. So we can see changing behavior in apa Subhramit Basu ***@***.***> schrieb am Sa., 3. Mai 2025, 19:24:

…

*subhramit* left a comment (subhramit/jabref#28) <#28 (comment)> Dumb me. — Reply to this email directly, view it on GitHub <#28 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACOFZDYOARKMRD34V6SKN324T3UHAVCNFSM6AAAAAB4L5HBZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNBYG4ZDCNBVHA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[subhramit]

Opened at JabRef#13052
(Apparently github allows us to change target branches within a repository, but not across fork and parent. Once opened with a target branch within my fork, I had an option to change to subhramit:main or any other branch within my fork but not JabRef:main).