In my currently still vague understanding, the main "aggregator part" would consist of a script which takes as input:
a wiki address
a revision id from the TW repo (the version from which the user started doing their changes)
remark: possibly, the revision could be found in the wiki itself
The script would:
package the changes as a git commit
send a pull request to the TW repo
there are several possible problems here, since a pull request can be done only if the requesting repo is up to date with the main repo.
afaik the only way to make sure that a commit can be applied is to create a new branch if a conflict occurs (?)
However it must be able to send a message to someone if something gets wrong. There is also the question of how it is called and receive the parameters (see Jeremy's ideas in the thread).
See thread https://groups.google.com/d/msg/Tiddlywiki/utB2C5QDjEs/OaW0qRJCAgAJ
In my currently still vague understanding, the main "aggregator part" would consist of a script which takes as input:
The script would:
However it must be able to send a message to someone if something gets wrong. There is also the question of how it is called and receive the parameters (see Jeremy's ideas in the thread).