Weles/Docs

CLI command

weles design export-assets

Export every Figma file in the explicit --request inventory, without organization-name filtering. The request names an existing clean checkout, one Git remote and branch, and the exact Skarbiec scope, item, field and workload identity. No repository is cloned or removed and no private account, SSH key, team or checkout is built in. The managed figma directory receives documents, nodes, assets and vocabulary; publication succeeds only after the remote branch reads back the new commit. The manual Actions form requires both runner_label and request_file and runs this same command. See the CLI reference's Design export section for the request format, prerequisites and retained failure state.

Purpose#

Export every Figma file in the explicit --request inventory, without organization-name filtering. The request names an existing clean checkout, one Git remote and branch, and the exact Skarbiec scope, item, field and workload identity. No repository is cloned or removed and no private account, SSH key, team or checkout is built in. The managed figma directory receives documents, nodes, assets and vocabulary; publication succeeds only after the remote branch reads back the new commit. The manual Actions form requires both runner_label and request_file and runs this same command. See the CLI reference's Design export section for the request format, prerequisites and retained failure state.

Invocation#

Usage
weles design export-assets --provider figma --request <export-request.json>

Options#

Options of weles design export-assets
OptionEffect
--providerThe provider a login, developer certificate, app password or account-security read goes through: apple for login and developer-certificate, google for app-password and account-security; none is assumed.
--requestweles --help names this option in the usage line and gives it no description.

Help#

`weles design export-assets --help` prints these usage lines and never runs the command.