Feature/codecheck status#137
Merged
Merged
Conversation
dxL1nus
force-pushed
the
feature/codecheck-status
branch
from
e90c526 to
999f8c6
Compare
Member
|
@dxL1nus Ping - take a look at the merge conflicts, please. |
…ating status, backend will be next
dxL1nus
force-pushed
the
feature/codecheck-status
branch
from
999f8c6 to
23d1cd4
Compare
nuest
requested changes
Jun 24, 2026
…echeck into feature/codecheck-status
Contributor
Author
should be fine now, as I recall, you only changed 2 locale strings correct? |
nuest
approved these changes
Jun 25, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes #33,
closes #32,
closes #61,
closes #119,
closes #121;
This PR introduces the CODECHECK Status to the Editorial Workflow.
The Status is therefore shown in the Side Bar of the CODECHECK Metadata Form.
For the status, the History is recorded, along with: status, time stamp, user_id & submission_id.
When the journal manager selects specific statuses in the settings form, then at least one of them has to be reached, in order to publish a paper. Otherwise the publication will be blocked and the user is informed, that the CODECHECK status is not enough to publish the paper.