-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Fix showing issues in your repositories #18916
Conversation
- Make a restriction on which issues can be shown based on if you the user or team has write permission to the repository. - Fixes a issue whereby you wouldn't see any associated issues with a specific team on a organisation if you wasn't a member(fixed by zeroing the User{ID} in the options). - Resolves go-gitea#18913
I don't think it will ask you have write permissions. We can define what's |
Yeah the current wording is bad, I've pushed a comment which makes the conditions more clearly. |
Codecov Report
@@ Coverage Diff @@
## main #18916 +/- ##
=======================================
Coverage ? 46.65%
=======================================
Files ? 854
Lines ? 122602
Branches ? 0
=======================================
Hits ? 57196
Misses ? 58514
Partials ? 6892
Continue to review full report at Codecov.
|
Yeah probably, but it seemed to be reproducibly simply. I for myself can test this at latest Monday. |
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.
Tested on Codeberg.org, seems to do what it should :)
Are you able to fix conflicts? |
Luckily not a big conflict. |
🚀 |
- Make a restriction on which issues can be shown based on if you the user or team has write permission to the repository. - Fixes a issue whereby you wouldn't see any associated issues with a specific team on a organization if you wasn't a member(fixed by zeroing the User{ID} in the options). - Resolves go-gitea#18913
-> #19191 |
- Make a restriction on which issues can be shown based on if you the user or team has write permission to the repository. - Fixes a issue whereby you wouldn't see any associated issues with a specific team on a organization if you wasn't a member(fixed by zeroing the User{ID} in the options). - Resolves #18913 Co-authored-by: Gusted <williamzijl7@hotmail.com>
* giteaofficial/main: Bump minimist from 1.2.5 to 1.2.6 (go-gitea#19194) Changelog for 1.16.5 (go-gitea#19189) (go-gitea#19192) Fix showing issues in your repositories (go-gitea#18916) Update issue_no_dependencies description (go-gitea#19112) Prevent redirect to Host (2) (go-gitea#19175) Prevent start panic due to missing DotEscape function Fix compare link in active feeds for new branch (go-gitea#19149) Redirect .wiki/* ui link to /wiki (go-gitea#18831) Try to prevent autolinking of displaynames by email readers (go-gitea#19169) Update HTTP status codes to modern codes (go-gitea#18063)
- Make a restriction on which issues can be shown based on if you the user or team has write permission to the repository. - Fixes a issue whereby you wouldn't see any associated issues with a specific team on a organization if you wasn't a member(fixed by zeroing the User{ID} in the options). - Resolves go-gitea#18913
@fnetX My local test instance isn't that complex as codeberg's, so I could've missed a edge case. Could you test this PR and see if this fixes the issue?