-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
[suggestion] "New Repository" on organization profile should default to current profile as owner #3253
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
Can a contributor please mark this as confirmed? It's bitten me (and my colleagues) a number of times, creating a personal repo instead of a shared repo as a result. (Note that github implements the desired behavior described.) |
Fix go-gitea#3253 Signed-off-by: Andrew Thornton <[email protected]>
OK I'm looking at this. There are a number of problems with the dashboard... |
|
* Create repository on organisation by default on its dashboard * Only show owners the add new repositories to an organisation button. Fix #3253 Signed-off-by: Andrew Thornton <[email protected]>
…ea#6026) * Create repository on organisation by default on its dashboard * Only show owners the add new repositories to an organisation button. Fix go-gitea#3253 Signed-off-by: Andrew Thornton <[email protected]>
…#6048) * Create repository on organisation by default on its dashboard * Only show owners the add new repositories to an organisation button. Fix #3253 Signed-off-by: Andrew Thornton <[email protected]>
When viewing an organization's homepage (e.g.
http://gitea/org/acme/dashboard
), and then using the "new repository" link in the menu bar up top, the default value of the "owner" field should be the organization that you were viewing (in this case,acme
) and not the logged-in user, presuming the user has permissions/rights to do so for the current organization.(Alternatively, a separate "Add repository" link could be added to the organization dashboard somewhere to create a new repository with the "owner" field defaulting to the currently-navigated organization.)
The text was updated successfully, but these errors were encountered: