Repository navigation
feat(html-documents): upload an organization's HTML library from the CLI - #221
Merged
Merged
Conversation
Add html-documents +upload, +list, folder +create, and +install-defaults. They call the org-scoped HTML document API with the selected organization and never send a parent id or a workspace. Co-authored-by: Weimeng Chen <MikeChenWM@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Mike, CTO, wants to upload HTML documents from the CLI into MuseOn's org-isolated HTML document library, setting a title and a default filename. The API is Museon-AI/museon#7516.
Changes
The commands follow this repo's action sigil and flag rules (a path is
--file, not a positional, and a folder id is--folder-id):museoncli html-documents +upload --file PATH --title TITLE [--filename NAME] [--folder-id FOLDER_ID]museoncli html-documents +list [--q TEXT] [--folder root|FOLDER_ID]museoncli html-documents folder +create --name NAMEmuseoncli html-documents +install-defaultsUpload POSTs
{title, html, filename?, folder_id?}to/api/v1/organizations/{org}/html-documentswith the CLI's existing auth andX-Organization-Id.filenameis--filename, or the file's basename when that basename is one*.html/*.htmname with no..or slash; otherwise it is omitted and the server names the file from the title. A path in--filenamecontributes only that basename.parent_idis never sent. Folder create POSTs{name}only.+install-defaultsPOSTs to.../defaultswith no body and does not duplicate guides on a second call.Tests
smoke_installreportedclean install smoke passed: version=2.2.0 commands=499.Release
This PR does not bump the version, tag, or publish a wheel.
Museon CLI ships as one wheel on a GitHub Release. The sequence in
docs/releasing.mdis: bump[project].versioninpyproject.toml(anduv.lock, the README, the install guide, and the bundled Skill), regenerate the command docs, contract, and task guide, merge tomain, then push tagv<version>on that commit..github/workflows/release.ymlruns onv*tags, checks the tag matches the package version and is an ancestor ofmain, runs the test suite, builds one wheel, and publishes the wheel, command contract, install guide, task guide, and skills archive.After that release, the museon repo needs
pnpm agent-cli:contract:syncso the agent command catalog learns these commands. #7516 did not change that catalog, and this PR does not either. The changelog entry belongs with the version bump.