Add units to team - #947
Conversation
|
This is done and could be reviewed. When add/edit a team on organization, you could chose which units could be organization's repositories operated on the by this team. For example, we can define |
There was a problem hiding this comment.
Do we really need External as a separate unit? Can we enable both internal wiki and external wiki at the same time? (same for Tracker)
There was a problem hiding this comment.
Why are we leaking information that this repo exists but have nothing to show? IMO no valid Units should be the same as Private.
There was a problem hiding this comment.
The error message is only for log. The UI will only show 404.
There was a problem hiding this comment.
Move this for easy add middleware contex.CheckUnit. Before this, releases URLs are put on many places.
|
LGTM |
e2da2af to
299b4e9
Compare
There was a problem hiding this comment.
Not an expert in xorm but can't .Where("1=1") be removed ?
|
This need rebase. |
|
@sapk rebased |
|
I know this PR is closed, but I believe I found an issue that might be related. I think this PR modified a lot of routes related to releases, I wonder if that has anything to do with it... |
|
@kubatyszko could you post an issue to describe that? |
This PR allows you create one team who can only see issues or pull request or wikis.