Add functionality for new events

[Leo-Send]

Adds functionality for the following events:

• issue_type_added
• issue_type_changed
• issue_type_removed
• connected
• reopened
• parent_issue_added
• parent_issue_removed
• sub_issue_added
• sub_issue_removed

[Leo-Send]

I have a few open questions/issues regarding this PR:

1. the 'connected' and 'subissue'/'parentissue' events do not contain any data on which issue the current issue is connected/related to. We could calculate this using timestamps, since both event types generate a counterpart in the connected/related issue. If we want to do this, I can look further into this.

2. Until now, I was unable to generate the 'sub_issue_changed' and 'parent_issue_changed' events. It seems to me that the only allowed interaction with subissues is adding or removing them. Should I still keep those events?

3. I am not sure about what I should do for the copyright headers, considering I only authored a change in one file so far.

Edit:
upon further investigation, all 'sub_issue' or 'parent_issue' event types do not appear in the REST api documentation. They do, however, appear in the graphQL api documentation and seem to behave the same in the REST api. But the 'sub_issue_changed' and 'parent_issue_changed' events do not exist there either.

[Leo-Send]

Quick update regarding connected events:
It is trivial to save the event id in the output json. Since this event id is the same for the connected events in both issues, it is then possible to find the related issue. The question in where we want to do that - in our toolchain, I think it would be sensible to do it in codeface-extraction or coronet. Adding this functionality to the GitHubWrapper would require a lot of work and I also do not think it fits here. It should be by far easiest in coronet, assuming we save the event id during the codeface-extraction issue processing, for example in event-info 1 or 2. If we do not want this id in the issues.list file, it can also be done in codeface-extraction.

[bockthom]

Good idea!

I agree, it does not fit into the GitHubWrapper. So, just store it in the json file and we will find the related issue later.
While both codeface-extraction and coronet would be suitable for doing that, I'd prefer to do that in codeface-extraction, for two reasons:

(1) We do all the other processing in codeface-extraction. Why should we leave this one post-processing step to coronet? Would be inconsistent, I guess.
(2) When we would do this in coronet, we would need to recompute the connected issues every time we read issue data. Why should we do this every time and spend additional compute resources on that? If we do that in codeface-extraction, we do it only once, and the issues.list files contain already the correct linkage.

So, I'd suggest to compute the connected issue in codeface-extraction.

[Leo-Send]

This PR is ready for review, but should be merged after PR #31 is merged.

[Copilot]

Pull Request Overview

This PR adds support for handling new GitHub event types related to issue management, specifically: issue type changes, state changes (reopened), parent/sub-issue relationships, and connected events. The changes enhance the existing GitHub API wrapper to capture and process these additional event types.

Key changes include:

• New data models for issue types (TypeData) and state reasons (StateReason)
• Support for tracking sub-issues and external commits
• Enhanced event processing for the newly supported event types
• Improved commit hash extraction by filtering out code blocks

Reviewed Changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
TypeData.java	New data model for issue type information from GitHub's API
StateReason.java	New enum for issue/PR state reasons (completed, reopened, not_planned, duplicate)
IssueDataProcessor.java	Added sub-issue parsing, external commit tracking, and code block filtering in hash extraction
IssueData.java	Added type field and sub-issues list to issue data model
GitHubRepository.java	Added external commit URL fetching and registered new event processors
GitHubCommit.java	Added external commit tracking flag
EventDataProcessor.java	Added processors for state change, issue type change, and connected events
EventData.java	Added new event data classes for state changes, issue type changes, parent/sub-issue changes, and connected events
README.md	Added documentation about referenced events and data processing

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[bockthom]

I am satisfied with the changes in this PR. However, we also need to satisfy Copilot in this and the previous PR.
If the previous PR is updated, I can merge that one right away, such that this one can be rebased on top of the other one.

[bockthom]

And please add you copyright header to StateReason.java, since you have modified it yourself now.

[Copilot]

Pull Request Overview

Copilot reviewed 11 out of 11 changed files in this pull request and generated 10 comments.

Comments suppressed due to low confidence (2)

src/de/uni_passau/fim/gitwrapper/EventDataProcessor.java:1

• The inner class StateChangedEventData is declared as public class inside EventData.java, but should be declared as public static class to match the pattern of other inner event classes like ReferencedEventData and LabeledEventData in the same file.

/**

src/de/uni_passau/fim/gitwrapper/IssueDataProcessor.java:431

• Variable 'String stateReasonValue' is never read.

        String stateReasonValue = (stateReasonElement != null && !stateReasonElement.isJsonNull()) 
            ? stateReasonElement.getAsString() 
            : null;

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.