Repository navigation
Go through devguide file-by-file for GitHub migration #39
Description
We need to go through the entire devguide for the GitHub migration. Having a module marked off as done means that it is ready to go in the github branch or a separate issue to track what needs to be done for a page has been created. The key point is that once every page is checked off there will be a clear understanding of what is left to do for the GitHub migration.
-
committing.rst(Update committing.rst for Git/GitHub #44) -
coredev.rst(Update coredev.rst for Git/GitHub #45) -
devcycle.rst(Update devcycle.rst for Git/GitHub #46) -
developers.rst(Update developers.rst for Git/GitHub #47) -
faq.rst(Delete the FAQ #27, Update FAQ.rst for Git/GitHub #48) -
gitdevs.rst(Update gitdevs.rst for Git/GitHub #49) -
index.rst(Update index.rst for Git/GitHub #50) -
patch.rst(Update patch.rst for Git/GitHub #51) -
setup.rst(Update setup.rst for Git/GitHub #52) -
triaging.rst(Update triaging.rst for Git/GitHub #53) -
buildbots.rst -
buildslave.rst -
clang.rst -
communication.rst -
compiler.rst -
coverage.rst -
coverity.rst -
docquality.rst -
documenting.rst -
experts.rst -
fixingissues.rst -
gdb.rst -
grammar.rst -
help.rst -
langchanges.rst -
motivations.rst -
runtests.rst -
silencewarnings.rst -
stdlibchanges.rst -
tracker.rst
Activity
brettcannon commentedon Oct 6, 2016
Now that there are separate issues for the remaining pages, the GitHub milestone can be used to track what's left to do.
Mariatta commentedon Dec 9, 2016
Do you want to check off these issues? Since they're closed already...
#44 #45 #47 #48 #49 #50 #51 #52 #53
#46 seems to be closed, but you mentioned about needing to make another PR.