Also, I often find that, when cleaing up a series of WIP ("Work In Progress," for any others who are listening in) commits to ready them for integration to the
master branch, the work of writing up a commit message that actually explains things well often finds problems and prompts me to go back and fix them. I guess it's along the same lines as the Readme Driven Development idea. I notice it particularly now because I keep meeting up with situations where someone's done a commit to make some tests pass, with no real explanation.* and when I ask them they don't really know what they did.
*My favourite commit message from today: "What the heck?" When I asked the guy, he said the tool he was using to comit wouldn't let him use "WTF?" as a commit message because it was too short.
masterbranch now has separate
--dev-releaseoptions so you can test your branch on your Netlify account, and we now have four sample wiki pages being served properly under the exact same
/wiki/...URLs as the current site uses, though we don't have links to pages with
:in the working (probably a fairly easy fix) or transcludes working (a more difficult fix, but in progress). The
dev/ejdm/wiki-fileshas the work we've started on a template for the Wiki pages. (Currently they display as very, very boring HTML with basically no markup.)
masterbranch describing the new hosting configuration and listing a few things we have to change. One is "Configure
tlug-jp.netlify.com." @E14n_twitter, can we get that done in the near future? Or can anybody else do it?
@E14n_twitter Can you have a look at my changes on
dev/cjs/190512/wiki-ns-link-fix? (These can currently be seen on https://cjs-tlug.netlify.com/.) There are two changes:
/wiki/) is correct.
/wiki/to the main page, as MediaWiki does.
masterand you can rebase your branch on to that at your convenience.
Comments from anybody else are welcome as well, of course.
META content-typeor whatever it is in the HTML
<HEAD>would help convince Firefox to do what we desire.