github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-13 02:57:44 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

API repos search should return private repos of that user #2974

New Issue
Closed
opened 2025-11-02 04:55:46 -06:00 by GiteaMirror · 9 comments
GiteaMirror commented 2025-11-02 04:55:46 -06:00
Owner
Copy Link

Originally created by @kasbah on GitHub (Feb 25, 2019).

Description

Hello and thank you very much for your work on gitea!

I think that similarily to #5310, GET /repos/search should return the private repos that the logged in user has access to. Currently only when you add uid=$CURRENT_USER_ID can you see the private repos (but then you don't see other people repos).

Changing this would make it behave more like the current /explore/repos non-api endpoint.

Originally created by @kasbah on GitHub (Feb 25, 2019). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 594f59169 ## Description Hello and thank you very much for your work on gitea! I think that similarily to #5310, `GET /repos/search` should return the private repos that the logged in user has access to. Currently only when you add `uid=$CURRENT_USER_ID` can you see the private repos (but then you don't see other people repos). Changing this would make it behave more like the current `/explore/repos` non-api endpoint.
GiteaMirror added the issue/confirmed label 2025-11-02 04:55:46 -06:00
GiteaMirror commented 2025-11-02 04:55:47 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Feb 26, 2019):

Isn't that fixed by #5383 ?

@lunny commented on GitHub (Feb 26, 2019): Isn't that fixed by #5383 ?
GiteaMirror commented 2025-11-02 04:55:48 -06:00
Author
Owner
Copy Link

@kasbah commented on GitHub (Feb 26, 2019):

No, unless I am missing something. I am testing on latest master (v1.7.0-dev-241-g594f59169). I guess it only fixed it for /orgs/:org/repos not /repos/search.

@kasbah commented on GitHub (Feb 26, 2019): No, unless I am missing something. I am testing on latest master (v1.7.0-dev-241-g594f59169). I guess it only fixed it for `/orgs/:org/repos` not `/repos/search`.
GiteaMirror commented 2025-11-02 04:55:48 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Feb 26, 2019):

I can confirm that this is still an issue and affects the organisation view on the dashboard.

@zeripath commented on GitHub (Feb 26, 2019): I can confirm that this is still an issue and affects the organisation view on the dashboard.
GiteaMirror commented 2025-11-02 04:55:48 -06:00
Author
Owner
Copy Link

@kasbah commented on GitHub (Feb 26, 2019):

@zeripath Could you clarify how it affects the organisation view on the dashboard? I had a look but couldn't find anything wrong there.

@kasbah commented on GitHub (Feb 26, 2019): @zeripath Could you clarify how it affects the organisation view on the dashboard? I had a look but couldn't find anything wrong there.
GiteaMirror commented 2025-11-02 04:55:48 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Feb 26, 2019):

OK, log in as arandomer2@mailinator.com with the same password on to http://try.gitea.io

arandomer2 has read access to TestOrgAnother, although TestOrgAnother/private-test-repository appears on arandomer2 dashboard take a look at:

https://try.gitea.io/org/TestOrgAnother/dashboard

@zeripath commented on GitHub (Feb 26, 2019): OK, log in as arandomer2@mailinator.com with the same password on to http://try.gitea.io arandomer2 has read access to TestOrgAnother, although TestOrgAnother/private-test-repository appears on arandomer2 dashboard take a look at: https://try.gitea.io/org/TestOrgAnother/dashboard
GiteaMirror commented 2025-11-02 04:55:48 -06:00
Author
Owner
Copy Link

@kasbah commented on GitHub (Feb 26, 2019):

Ah I see. Is that an experimental page or something? I am not even sure how to even get there through the UI. Nevermind, figured out it's through the top left selection on the dashboard. Not sure what it's for though vs just the gitea.com/<org-name> page.

@kasbah commented on GitHub (Feb 26, 2019): Ah I see. <del>Is that an experimental page or something? I am not even sure how to even get there through the UI. </del> Nevermind, figured out it's through the top left selection on the dashboard. Not sure what it's for though vs just the gitea.com/\<org-name\> page.
GiteaMirror commented 2025-11-02 04:55:48 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Feb 26, 2019):

It's supposed to give you the newsfeed for that organisation context. The + repository button would allow you to create a repository in that organisation by default if you're allowed to create repositories for that organisation.

@zeripath commented on GitHub (Feb 26, 2019): It's supposed to give you the newsfeed for that organisation context. The + repository button would allow you to create a repository in that organisation by default if you're allowed to create repositories for that organisation.
GiteaMirror commented 2025-11-02 04:55:48 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Feb 26, 2019):

I don't think you're supposed to see the organisation repos in the right hand box unless you're in the organisation context either

@zeripath commented on GitHub (Feb 26, 2019): I don't think you're supposed to see the organisation repos in the right hand box unless you're in the organisation context either
GiteaMirror commented 2025-11-02 04:55:49 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Oct 16, 2019):

I think this is finally fixed by #6897 in 1.9

@zeripath commented on GitHub (Oct 16, 2019): I think this is finally fixed by #6897 in 1.9
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/confirmed
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2974
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?