You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 27, 2026. It is now read-only.
Currently, we use the REST APIs of the different forges. There is a difference between the APIs that results in different behaviours. For instance, GitHub includes PRs in their issues Endpoint. So we need to filter the PRs after we've fetched them. This may result in a wrong amount of issues shown to the user, e.g. we may fetch 100 "issues" via --per-page but only 50 may be shown to the user, if the other 50 are actually PRs.
So let's investigate if forges offer alternative APIs that may lessen the differences. GitHub, as an example, seems to also offer a GraphQL API.
Currently, we use the REST APIs of the different forges. There is a difference between the APIs that results in different behaviours. For instance, GitHub includes PRs in their
issuesEndpoint. So we need to filter the PRs after we've fetched them. This may result in a wrong amount of issues shown to the user, e.g. we may fetch 100 "issues" via--per-pagebut only 50 may be shown to the user, if the other 50 are actually PRs.So let's investigate if forges offer alternative APIs that may lessen the differences. GitHub, as an example, seems to also offer a GraphQL API.