This repository has been archived by the owner on Feb 8, 2018. It is now read-only.
move Members over one #3078
Merged
move Members over one #3078
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Receiving and Giving go together conceptually, and Members is actually less private than Receiving, since Receiving can be hidden but Members can't (once you're a team).
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In general I like the reordering of profile subnav that @Changaco did in c0275a5 on #2938. However, I think Members shouldn't come between Receiving and Giving, because Receiving and Giving go together conceptually, and Members is actually less private than Receiving, since Receiving can be hidden but Members can't (once you're a team).