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

Remove direct user adding to organization members #2641

Merged
merged 2 commits into from
Oct 15, 2017

Conversation

lafriks
Copy link
Member

@lafriks lafriks commented Oct 2, 2017

Reason for this as this button is very confusing and there is no much point in adding user directly as organization member he will still not be able to do anything more than if he would not be added. It just makes people more confusion why user can not access or do anything. Users should be to added to repository members by adding user to one or more this organization team

@lafriks lafriks added the type/refactoring Existing code has been cleaned up. There should be no new functionality. label Oct 2, 2017
@lafriks lafriks added this to the 1.3.0 milestone Oct 2, 2017
@codecov-io
Copy link

codecov-io commented Oct 2, 2017

Codecov Report

Merging #2641 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #2641   +/-   ##
=======================================
  Coverage   27.12%   27.12%           
=======================================
  Files          87       87           
  Lines       17176    17176           
=======================================
  Hits         4659     4659           
  Misses      11837    11837           
  Partials      680      680

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f42dbdb...1eebcb7. Read the comment docs.

@tboerger tboerger added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Oct 2, 2017
@lafriks lafriks mentioned this pull request Oct 7, 2017
7 tasks
@Morlinest
Copy link
Member

LGTM

@tboerger tboerger added lgtm/need 1 This PR needs approval from one additional maintainer to be merged. and removed lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. labels Oct 14, 2017
@lafriks lafriks force-pushed the remove_direct_memeber_adding branch from 1dcde5e to 1b18e91 Compare October 14, 2017 18:48
@lunny
Copy link
Member

lunny commented Oct 15, 2017

So why github has this feature?

@lafriks
Copy link
Member Author

lafriks commented Oct 15, 2017

@lunny because in github that actually grants some rights for members (like creating new repositories under that organization and new teams) while in Gitea it does nothing and all rights are checked only by team. And to be honest Gitea way to me seems a lot better and could be used for more use cases

@lunny
Copy link
Member

lunny commented Oct 15, 2017

LGTM

@tboerger tboerger added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Oct 15, 2017
@Morlinest
Copy link
Member

One question before sleep. What about users that was added this way? Do you want to ignore it or make migration to remove them?

@lunny
Copy link
Member

lunny commented Oct 15, 2017

@Morlinest they will stay the same behavior with before. Organization owners could remove them from organization or add them to some teams.

@lafriks
Copy link
Member Author

lafriks commented Oct 15, 2017

They do not do any harm so they can stay. This change is just so that it would be less confusing and there would not be regular questions and issues that user is added to org. members but he still does not see nor can do anything

@lunny lunny merged commit 32ca299 into go-gitea:master Oct 15, 2017
@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. type/refactoring Existing code has been cleaned up. There should be no new functionality.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants