Hey Jeremy, A couple questions for you:
1. Does this mean that every merged PR will quickly show up on the prerelease? 2. Should this cause any changes to the contribution process as outside contributors? Matt Lauber On Tuesday, January 8, 2019 at 10:41:59 AM UTC-5, Jeremy Ruston wrote: > > Up until now, making updates to tiddlywiki.com has been a tedious > process: the grimy technical details are that I merge a pull request on > github.com, and then back on my laptop, I have to pull the changed > repository down from GitHub, and then run a script to build the site, and > another to upload it to GitHub. > > Being so time consuming and inconvenient has meant that we’ve struggled to > make timely updates to tiddlywiki.com. I know that this has been a source > of discouragement to contributors, and so I’m very happy to have finally > been able to address it. > > I’ve now enabled “continuous integration” for the TiddlyWiki 5 repo. This > means that the site is automatically rebuilt every time a PR is merged or a > commit is pushed, without any further manual intervention. It means that I > can accept documentation updates and publish them from my phone/tablet > sitting on a train. > > The main implication for contributors is that documentation PRs should now > target the “tiddlywiki-com” branch instead of “master”. (I can change > existing PRs as I merge them). I’ll update the docs shortly to make this > clear. > > The technical details of the changes are discussed on this GitHub issue: > https://github.com/Jermolene/TiddlyWiki5/issues/3115 > > Comments, questions etc. welcome, > > Best wishes > > Jeremy > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/b0af132f-7626-4cc4-8e13-c0f7ab1152ea%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
