Skip to content

Refactor codebase to split Issue and PullRequest #464

@IzN432

Description

@IzN432

Currently, the code that was taken from CATcher has all Issues and PRs as under the Issue class, differentiated by the IssueOrPr field. This is not very good practice, and has caused quite a bit of confusion.

We should refactor this into two separate classes, Issue and PullRequest.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions