Skip to content

Feature/reserve identifier with new issue url#118

Draft
dxL1nus wants to merge 25 commits into
codecheckers:mainfrom
dxL1nus:feature/reserve-identifier-with-new-issue-url
Draft

Feature/reserve identifier with new issue url#118
dxL1nus wants to merge 25 commits into
codecheckers:mainfrom
dxL1nus:feature/reserve-identifier-with-new-issue-url

Conversation

@dxL1nus
Copy link
Copy Markdown
Contributor

@dxL1nus dxL1nus commented May 3, 2026

Closes #99,
closes #62,
closes #53,
closes #104,
closes #55,
closes #100,
closes #101,
closes #125

This PR is a massive one, but needed as most of the functionality is based upon each other, although there are a number of features addressed here.

Features that come with this PR:

  • Reserving identifiers with a GitHub New Issue URL Link
  • Linking manually created GtiHub Issue to the Certificate Identifier in OJS Submission
  • Update the information in the GitHub Issue (on metadata form save)
  • Delete concept of Venue Type & Venue Name as Labels (instead all labels in one central Dropdown)
    • Labels are cached / saved in the OJS DB (and only fetched from the API, when they are older than 6 hours)

❗This PR should be merged before #109 as I want to include a setting in the settings form for a feature which is only introduced with this PR here (#101).

dxL1nus added 24 commits May 3, 2026 18:01
…a DB

# Conflicts:
#	CodecheckPlugin.php
#	api/v1/CodecheckApiHandler.php
# Conflicts:
#	api/v1/CodecheckApiHandler.php
…ved automatically, then issue will be automatically linked as well
…rl exists and Input has some characters inputted
…etched, now issues are fetched by being searched directly for the identifier in the title
@dxL1nus dxL1nus requested a review from nuest May 3, 2026 16:47
@dxL1nus dxL1nus marked this pull request as draft May 3, 2026 16:48
@dxL1nus
Copy link
Copy Markdown
Contributor Author

dxL1nus commented May 3, 2026

so far this is a draft, because all parts are finished except for Issue #100. @nuest do we need this issue here in this stage already or can it be introduced at a later stage, so we can merge this PR. What do you think?

@dxL1nus
Copy link
Copy Markdown
Contributor Author

dxL1nus commented May 3, 2026

Plus it is a draft still, because I need to fix the unit tests here, which so far don't work

@dxL1nus
Copy link
Copy Markdown
Contributor Author

dxL1nus commented May 4, 2026

Plus it is a draft still, because I need to fix the unit tests here, which so far don't work

So far I fixed nearly every unit test apart from two, as I am not quite sure how to fix them yet (I will look into it further).

I will definitely also need to add some new unit tests as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment