Repository navigation
Conversation
rmunn
added
engineering
Unit Test Results362 tests 362 ✅ 8s ⏱️ Results for commit b31b4f9. ♻️ This comment has been updated with latest results. |
Written by Claude Code (mostly Opus 5, some Opus 5.5), tested on local dev machine. Some projects, those with custom fields created in LF, will need a two-step process: run the script once, which will determine the XML to put into the FW project in order to define the custom fields. Then clone the Mercurial repo, add that XML as a new Mercurial commit, and push that commit to Lexbox. Then run the script again. The script is intended to run on the Language Forge `app` container, and that container cannot push Mercurial repos to LexBox, so the custom-fields commit needs to be a manual process. There are only six projects that look like they will need this, however, so it's not as onerous as it might sound. For all other projects, the script will run as-is without any manual steps. Once the script runs, there will be a `(projectCode)-migrate` project on the server with a copy of the project's data, and a new LexBox project with the same `(projectCode)-migrate` name that contains the project's data in FW format. That data can then be brought into FieldWorks Lite.
2344f04 to
b31b4f9
Compare
|
I am actually slightly disturbed that all checks have passed on this PR, because it shows there's a hole in our checks. I deliberately specified a version of the Probably not worth investing time to fix the checks on a server we're planning to sunset, but I did want to mention that the "mistake" in |
Written by Claude Code (mostly Opus 5, some Opus 5.5), tested on local dev machine.
This is a Python script to migrate the projects identified in sillsdev/languageforge-lexbox#2414 as being worth migrating to LexBox and FW Lite. It needs sillsdev/LfMerge#361 and sillsdev/languageforge-lexbox#2439 to be merged first before the script can run.
Some projects, those with custom fields created in LF, will need a two-step process: run the script once, which will determine the XML to put into the FW project in order to define the custom fields. Then clone the Mercurial repo, add that XML as a new Mercurial commit, and push that commit to Lexbox. Then run the script again. The script is intended to run on the Language Forge
appcontainer, and that container cannot push Mercurial repos to LexBox, so the custom-fields commit needs to be a manual process. There are only six projects that look like they will need this, however, so it's not as onerous as it might sound.For all other projects, the script will run as-is without any manual steps. Once the script runs, there will be a
(projectCode)-migrateproject on the server with a copy of the project's data, and a new LexBox project with the same(projectCode)-migratename that contains the project's data in FW format. That data can then be brought into FieldWorks Lite.