Skip to content

fix(ng-dev): order results of forks when searching for user owned forks #796

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

josephperrott
Copy link
Member

It appears that Github has made a change, or has introduced a bug in which unsorted results of forks for a repository with OWNER affiliation are returned as empty. Once ordering is provided the results show again as expected. While this should not be necessary, it is an innocuous change for us that is fine to remain indefinitely.

It appears that Github has made a change, or has introduced a bug in which unsorted results
of forks for a repository with OWNER affiliation are returned as empty.  Once ordering is
provided the results show again as expected.  While this should not be necessary, it is an
innocuous change for us that is fine to remain indefinitely.
@josephperrott josephperrott added the action: merge The PR is ready for merge by the caretaker label Aug 25, 2022
Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Super weird bug, can confirm the fix works.

@josephperrott can you capture the GitHub ticket outcome here?

@angular-robot
Copy link
Contributor

angular-robot bot commented Aug 25, 2022

This PR was merged into the repository by commit 806c568.

@angular-robot angular-robot bot closed this in 806c568 Aug 25, 2022
@josephperrott
Copy link
Member Author

@devversion will update once I have a response.

@josephperrott josephperrott deleted the fix-fork-finding branch August 25, 2022 14:57
@josephperrott
Copy link
Member Author

It appears that whatever change was made that caused the issue was rolled back and the requests now return as expected.

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants