Ok, that's the single line, which is put at the top instead of into the step-by-step directions:
If you already know GitHub <https://tiddlywiki.com/#GitHub>, note that > documentation updates must be directed to the tiddlywiki-com branch > I don't know what it means by "directed to the tiddlywiki-com branch." Does that mean my branch is a sub-branch of the tiddlywiki-com branch? Or do I call my branch tiddlywiki-com ? For most of us, Github is not really very friendly. It often gives messages that are confusing and counter-intuitive. We need all the help we can get. Thanks! On Friday, December 6, 2019 at 6:51:45 AM UTC-8, Jeremy Ruston wrote: > > Hi Mark > > On 6 Dec 2019, at 14:48, 'Mark S.' via TiddlyWiki < > tiddl...@googlegroups.com <javascript:>> wrote: > > The change to the documentation system itself was only documented with a > single line. Or maybe not even that. I don't know what it means to work on > the documentation branch. Do I make a branch below the documentation > branch, or call my own branch by that name? > > As far as I can tell, the tiddler, > > Improving TiddlyWiki Documentation > > was not updated to reflect the changes. > > Thanks! > > > That tiddler was indeed updated back in January when we introduced the > change. From the perspective of the person making the PR the only thing > that changed was that the PRs should now target the “tiddlywiki-com” branch > (hence the docs update). All the good changes are in the background: now > when I merge a PR it automatically triggers a rebuild of tiddlywiki.com > whereas > in the past I needed to run the update from my computer, and it took a > considerable time. > > Best wishes > > Jeremy. > > > > > On Friday, December 6, 2019 at 2:16:47 AM UTC-8, Jeremy Ruston wrote: >> >> A couple of thoughts: >> >> * Pinning should never have been globally available. I appreciate the >> argument that no great harm was done, but it evidently created confusion as >> to who could see that a thread had been pinned >> * We should agree on general rules for what threads might qualify for >> being pinned. To me, pinning would start with urgent announcements (e.g. if >> discovered a serious bug in a release and wanted to warn people to >> upgrade), important on-going informational threads like “Newbies start here” >> * Generally I think it might be interesting to experiment with more use >> of pinned threads that are updated by an admin (e.g. we could have a thread >> “Announcements December 2019” that a volunteer like (say) Mohammad might >> undertake to update on a regular basis) >> * As to plugin announcements, maybe the route to the widest audience is >> to put them on tiddlywiki.com. For a year now we’ve had the ability to >> do near instantaneous updates to tiddlywiki.com just by merging a pull >> request. It’s a shame we haven’t seen more use made of this; for the first >> time, tiddlywiki.com is editable by anyone who can create a PR >> * We can appoint as more group managers if we need to >> >> Best wishes >> >> Jeremy >> >> On 6 Dec 2019, at 09:45, TonyM <anthon...@gmail.com> wrote: >> >> Bit of a storm in a tea cup >> >> I had never pinned anything before. Found I could and assumed it was >> private. Two other pins occurred then I found out it was public and started >> a pin exit plan. >> >> As far as I can see this has being the extent of pins in the last year or >> more so, with respect, I suggest education before restricting or dictating. >> >> This is only my opinion but I have seen dozens of forums fail by the >> overzelouse slippery slope arguements that gradually disable features, >> create moderator roles where none were necessary, all due to perceived only >> possibilities. >> >> As soon as you remove member responsibility you stop them taking >> responsibility. >> >> By the way my two pins received substantial contributions as a result, to >> a community wide need. >> >> Please solve problems by education first, not reducing things to an >> imaginary lowest common denominator. >> >> Sincerly >> Tony >> >> -- >> You received this message because you are subscribed to the Google Groups >> "TiddlyWiki" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to tiddl...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/tiddlywiki/c508d140-c1c8-4d3c-9e04-60f08190be15%40googlegroups.com >> . >> >> >> > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWiki" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to tiddl...@googlegroups.com <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/52466f0d-3ff4-4b17-b0c6-c9975d5d3d1c%40googlegroups.com > > <https://groups.google.com/d/msgid/tiddlywiki/52466f0d-3ff4-4b17-b0c6-c9975d5d3d1c%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/d1d7ff9c-ff8c-4a02-a23c-32f9b8f78e1c%40googlegroups.com.
