Does too much magento* count as an excuse? :grin:
Maybe
Awesome!!
@carusogabriel
@heiglandreas Have you seen this? http://news.php.net/php.doc/969387146 :heart:
COmpletely skipped my inbox :)
Awesome!
Why does life always need to happen .... :-D
GitHub mirror here: https://github.com/php/web-doc
And edit.php.net is at http://git.php.net/?p=web/doc-editor.git;a=summary and https://github.com/php/web-doc-editor
Which has this interesting looking PR open... php/web-doc-editor#3
It's very old, but maybe useful
This is the misspell fixer I talk about, but I'm going to search for some build on top of CIs
This repo https://github.com/danack/PHPDocTool will do all the stuff necessary to check out the docs, and PHD then render it locally, and watch for any changes on the file system, at which point it will rebuild just the changes.
The good news is rebuilding just the changes in isolation is really quick (a few seconds) the less good news is that because the build is done in isolation, there is some stuff missing e.g. if you make a change in Imagick::adaptiveBlurImage, that page will be updated.......but it will lose all links to other Imagick methods, because the class index was included in the partial render.
btw, that tool currently uses
git ls-files -m to find the modified files. This apparently makes Docker very angry, and shouldn't be left running indefinitely.
@salathe Do the repos for the doc-base and the PHD renderer have tests setup for them? Obviously using the same code that is actually run to build the manual as for CI and local tools would be good, but I think I'd like to make some changes to configure.php in doc-base, and possibly the PHD renderer to make it possible to i) call them as functions rather than having to invoke them through the command line ii) be able to compile small chunks of the manual, in a way that produces an output that is more like the full manual build rather than the current partial rendering, due to the indexes being lost.
If they have tests, then making changes would be reasonably safe.....if not, then no.
I'm going to play with the github notifications next and look at rendering pull requests.....I'm going to stick with a separate tool rather than just using Travis for now, as I still think having the build results be almost instantaneous and viewable online will be better than Travis which can lag and would need to have the results pushed somewhere else to be viewed.
But ....it is possible that I might change my mind and just shove it in favour of Travis.
I've been played with the misspell-fixers and Travis