You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 28, 2018. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 28, 2018. It is now read-only.
Documentation should be merged into code repository #3
Currently, the documentation is somewhat out of sync with the codebase, and has had much less attention. I suspect that at least some developers working on the codebase aren't even aware that the documentation repository exists. Keeping the two in the same repository might help alleviate this problem.
Thanks!
P.S. I've asked for the contents to be merged into a documentation subdirectory of the codebase's master, rather than into a documentation branch. This is because if a developer begins work on a fix or feature by branching from master, then their new fix/feature branch will contain the documentation directory, making it obvious and easy for the developer to update the documentation appropriately in that branch, and keeping the documentation update and the fix/feature in sync.
If the documentation were, instead, in its own branch, which I don't advocate, then the workflow for the developer would be more laborious. They would have to create two feature/fix branches: one from the master branch and one from the documentation branch. And then they would have to keep their code feature/fix branch and documentation feature/fix branch in sync. It would be almost as bad as the current unhappy situation of having the documentation and codebase in separate repositories.
Activity
ghost changed the title [-]Documentation in separate repo to code[/-][+]Documentation should be merged into code repository[/+]on May 27, 2016
Activity
[-]Documentation in separate repo to code[/-][+]Documentation should be merged into code repository[/+]