Skip to content
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

Closed
mqudsi opened this issue Dec 22, 2017 · 4 comments · Fixed by #6026
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented

Comments

@mqudsi
Copy link
Contributor

mqudsi commented Dec 22, 2017

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.)

@stale
Copy link

stale bot commented Feb 9, 2019

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.

@stale stale bot added the issue/stale label Feb 9, 2019
@mqudsi
Copy link
Contributor Author

mqudsi commented Feb 9, 2019

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.)

@stale stale bot removed the issue/stale label Feb 9, 2019
@lafriks lafriks added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Feb 9, 2019
zeripath added a commit to zeripath/gitea that referenced this issue Feb 9, 2019
@zeripath
Copy link
Contributor

zeripath commented Feb 9, 2019

OK I'm looking at this. There are a number of problems with the dashboard...

@zeripath
Copy link
Contributor

zeripath commented Feb 9, 2019

/api/v1/repos/search?uid={{ORG_ID}}&q=&limit=15&mode= doesn't give the same results as the /{{ORG_NAME}} profile page.

zeripath added a commit that referenced this issue Feb 10, 2019
* 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]>
zeripath added a commit to zeripath/gitea that referenced this issue Feb 12, 2019
…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]>
techknowlogick pushed a commit that referenced this issue Feb 13, 2019
…#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]>
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants