So, regarding classic.tiddlywiki.com.. Is it correct that editing it can be done by just (forking and) cloning the [1] repo and editing TW in a browser? (and pushing back to fork and merging) I mean are recipes at [2] outdated since TiddlySpace is down (so [2] now has nothing to do with [1] and classic.tiddlywiki.com)?
No, wait, this can't be. First, TW version won't be updated this way (as well as the download package). Second, which is more surprising, for now I have only cloned [2] and still got cooked/2.9.1/index.html with classic.tiddlywiki.com's content in it once I've cooked TW.. is content from [1] accounted at all? Any suggestions? What's the correct workflow? Yeah, the last change was done back in 2013, so it won't surprise me if nobody remembers... Best regards, Yakov. [1] https://github.com/TiddlyWiki/tiddlywiki.github.com [2] https://github.com/TiddlyWiki/tiddlywiki.com/ среда, 24 января 2018 г., 17:56:27 UTC+3 пользователь PMario написал: > > On Wednesday, January 24, 2018 at 2:09:11 PM UTC+1, Yakov wrote: >> >> PS is that correct that the upstream name is purely a convention and git >> doesn't do anything different with regard to it, technically? >> > > Yes ... All aliases are just a convention. ... If you use the same schema > for all your local repos, it helps to minify "user errors" > > For me "push origin" means ... I can savely write to it. > > "push upstream" means ... Be really carefull ... Messing it up, will > cause a lot of work to fix it! > > -m > -- 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/e69479ec-a459-4880-af5d-1ed95ae1a979%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
