PullRequestConnection uses IssueOrder instead of PullRequestOrder

[marcduiker]

I noticed that when ordering PullRequests the IssueOrder enum is being used instead of the PullRequestOrder enum:

octokit.graphql.net/Octokit.GraphQL/Model/Ref.cs

Line 30 in e92b6c4

public PullRequestConnection AssociatedPullRequests(Arg<int>? first = null, Arg<string>? after = null, Arg<int>? last = null, Arg<string>? before = null, Arg<string>? baseRefName = null, Arg<string>? headRefName = null, Arg<IEnumerable<string>>? labels = null, Arg<IssueOrder>? orderBy = null, Arg<IEnumerable<PullRequestState>>? states = null) => this.CreateMethodCall(x => x.AssociatedPullRequests(first, after, last, before, baseRefName, headRefName, labels, orderBy, states), Octokit.GraphQL.Model.PullRequestConnection.Create);

The query works, so there no loss in functionality. It is just a bit unintuitive. I understand this model is generated, I'm not sure where this could be fixed. If you can give any pointers I'm happy to look into it and submit a PR.

[github-actions]

👋 Hey Friends, this issue has been automatically marked as stale because it has no recent activity. It will be closed if no further activity occurs. Please add the Status: Pinned label if you feel that this issue needs to remain open/active. Thank you for your contributions and help in keeping things tidy!

[kfcampbell]

PRs are issues underneath the hood, which is why they share some models. They share the same IDing system as well: if you navigate to issue #236, it redirects to PR #236.

I agree that it's a bit unintuitive, but it is expected.