Repository navigation
v0.1.1
Fixes a push --apply bug in v0.1.0 that could leave a page impossible to push.
Upgrade if you use --apply.
Fixed
- A page could become permanently unpushable. When an edit changed nothing on
the wiki (for example, an editor added a final newline, which MediaWiki trims
on save), v0.1.0 recorded revision 0 as the page's baseline. Every later push
of that page was then refused withremote moved to rev N (baseline rev 0).
pushnow reads back the revision the wiki actually stored and records that.
(#9) - The baseline drifted from the wiki.
pushrecorded the text it sent, not
the text MediaWiki saved. After a push, the baseline and your local file now
match what the wiki stored. Behaviour change: your local file may be
rewritten slightly, e.g. trailing whitespace removed. (#9) - Unhelpful errors. API errors now show MediaWiki's own code and message
(e.g.readapidenied) instead ofno page in response. (#10)
Added
- Per-wiki credentials.
push --applyreadsWIKISYNC_USERNAME_<WIKI>and
WIKISYNC_PASSWORD_<WIKI>, with<WIKI>derived from the host
(www.appropedia.org→APPROPEDIA), falling back toWIKISYNC_USERNAME/
WIKISYNC_PASSWORD. It reports which variable it logged in from. (#11)
Testing
- The push round-trip now runs against a throwaway MediaWiki 1.45 in Docker on
every change. It checks sync state after each push, that a repeated push is a
no-op, that a null edit creates no revision, and thatpushrefuses to
overwrite a change made on the wiki (#10). Run it locally with
just test-integration, or against a real wiki withjust test-live(#7).
Status
push --apply is still experimental: it is tested against MediaWiki 1.45
in CI, but not yet against Appropedia itself (#12). pull, status, diff and
push preview mode have been run against Appropedia.