This repository has been archived by the owner on Jun 3, 2019. It is now read-only.
Adding 'Community forks and extensions' to the README #527
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
|
@ALL - Please add yours to the list in the README once this is merged. |
|
Awesome pr @oyeanuj, great idea! |
|
Would be great if people could start lifting the feature branches they care about into their own github accounts and then updating the docs. Also then please let me know when you have done so. I would like to kill the feature branches as it's just too much to maintain ontop of the repo itself. |
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.
This adds a section for community forks in the README, addressing #504, and sets us up for reducing feature branch maintainence load.