Feature/codecheck status#142
Merged
Merged
Conversation
…tus in GitHub register issue now implemented codecheckers#132
dxL1nus
force-pushed
the
feature/codecheck-status
branch
from
July 13, 2026 10:30
18966cc to
e68df4f
Compare
dxL1nus
marked this pull request as ready for review
July 13, 2026 11:15
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
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 #132,
closes #141;
! IMPORTANT: Needs #139 to be merged first
CODECHECK Status Update: Based on the OJS workflow, create a list of "events" that are worth documenting in the register (article reviewed, editorial decisions (reject), certificate published, ...). This is related to #32 and what kind of information can be publicly revealed when.
Fix CODECHECK status information, when CODECHECK was not yet started / is pending
act on pending behavior when it is checked if CODECHECK was already started in publication update