Conversation
see tj#358 * wiki/master: (30 commits) git merge-repo add wiki for git-guilt Update docs for revised git-changelog. add wiki for git-merge-into git scp tj#300 link to git delta git delta usage Add git-authors Updated Commands (markdown) Updated Commands (markdown) Updated Commands (markdown) Updated Commands (markdown) Updated Commands (markdown) Fix link to git feature command Added a footer. add a few keywords some remaining dashes roughly finished Updated Commands (markdown) Updated Commands (markdown) ...
Collaborator
|
👍 Shall I merge after the wiki is updated? |
Collaborator
|
Ping @chernjie |
Contributor
Author
|
Oh sorry, I missed your message. By "updating wiki", I mean to delete all the contents there, linking back to main repository. Are you okay with that? For release, yes you can merge this. We can always update the wiki later. |
Collaborator
|
Just like back to the readme in wiki would be good, as people might go to wiki to read the docs, I'll merge this for now, Thank you! |
hemanth
added a commit
that referenced
this pull request
Apr 27, 2015
Merge wiki into main repository
Collaborator
|
Just like back to the readme in wiki would be good, as people might go to wiki to read the docs, I'll merge this for now, Thank you! |
Contributor
Author
|
Wiki updated with the relevant links :) |
Collaborator
|
👍 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
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.
Closes #358
TL;DR
Documentation should be in the same git repo as it's main project
Long version
I understand
git-extrashave recently moved the long winded contents ofReadme.mdinto Github's wiki. It is a good thing asReadme.mdhas become too long and at some point has become difficult to maintain.Having said that, I do think that the
HEADof each wiki ref should stay in sync with theHEADof each pull request. This ensures that documentations are not left out and encourage script discovery.@hemanth has been tirelessly advising pull requesters to update the wiki on every successful review. Perhaps we could be suggested that unless documentations are updated, the PR will not be merged?
Proposed solution (simple)
Since Github's wiki is also a Git repo, we can merge it into the main repo without losing history or
refheads. Effectively retiring Github wiki.Follow up task