Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Allow cross-repository dependencies on issues #7901
Allow cross-repository dependencies on issues #7901
Changes from 25 commits
86442ad
ce3312a
f33a34b
6647aa8
f1bae29
935eae4
0473eca
52f0e19
0b9e67b
b426606
2f257d0
3c78743
662cf44
4e90f86
6d741b7
cf015b6
e630aa7
2af7328
1b08937
3a5f40b
deb2ff3
b7cd0f5
a707ea7
25c40a4
3a9028f
9dd2fc0
e629f7e
0327365
17b7888
2ab1058
690442c
cf36916
ea04606
49b7d2a
2ec084d
c77a950
c19468c
171465c
50680e4
074edcf
ddd3488
1d8bd09
22c5dd2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mmm.... If you sort by issue.id DESC you get the newer issues first, which would make sense. Order by repository ID makes no sense. It's an internal number.
Perhaps:
would cause the issues from the current repo to show first.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
gotcha, these are for the list of blocked by or blocking dependencies displayed on the issue page (i.e. not the drop-down list to add a new one). I was thinking it would make sense for the issues to be in order of their id grouped by repo, so you'd see all the "repo1" issues and then "repo2" issues, not mixed together. But I agree with your suggestion, thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, I see! To group by repo and still have the current repo top of the list:
But I've got confused. I thought this was for the search function.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for the suggestion, I used the order by statement you suggested
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you should pass the repo id or name, and prioritize issues from that repository. There can be thousands of issues in a Gitea installation (Gitea alone has passed 8200).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks, this is done now