[ENG-8185] Unit tests for Manual GUID and DOI #11175
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… disabledx when it must
opaduchak
changed the title
opaduchak
changed the title
cslzchen
merged commit bb62bed
into
CenterForOpenScience:feature/manual-guid-and-doi-assignment
6 checks passed
cslzchen
added a commit
that referenced
this pull request
Jun 11, 2025
…ns - BE (#11174) * [ENG-8147] Manually assign GUID when creating registrations and preprints (#11160) * [ENG-8145] Added manual doi setting for registrations and preprints (#11162) * [ENG-8145] Update manual DOI assignment for Preprints (#11172) * Revert unnecessary changes in generate_guid() (c46e21b) * Allow blank value when manually setting GUID and DOI (2b09d94) * [ENG-8185] Unit tests for Manual GUID and DOI (#11175)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
Add unittests for manual guid and doi asignment
Changes
QA Notes
Please make verification statements inspired by your code and what your code touches.
What are the areas of risk?
Any concerns/considerations/questions that development raised?
Documentation
Side Effects
Ticket