We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
docs: update project structure references to use Solution/ instead of Package/ and clarify project file naming conventions
docs: push deletes a Custom API only when it can prove it owns it Rewrites the multi-project deletion section around positive attribution: an API implemented by a plugin type this push owns and no longer declared in source. Anything else is left alone, and an API with no implementation needs --force delete-orphans. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MMQgPwUsApt7EXYKhk3Y58
docs: document multiple plugin projects and multi-project orphan scope Covers discovery by solution-file membership, when splitting projects is worth it, and what push deletes once a solution has siblings — including why pushing the whole solution rather than a subset is what keeps the orphan set correct. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MMQgPwUsApt7EXYKhk3Y58
docs: update links and references across multiple documentation files; add new Push WebResources guide
Add migration guides for Daxif, PACX, and ALM Accelerator; introduce planned features - Created migration guide from Daxif detailing equivalent commands and migration steps. - Added migration guide from PACX outlining command mappings and two-phase migration strategy. - Developed migration guide from ALM Accelerator, emphasizing deployment model changes and mapping to Flowline commands. - Introduced a new document for planned features, including post-deploy state reconciliation and CLI setup enhancements.