CI automation is not documented

What it does

CI automation is not documented for DemoVexa. There is no documented claim here for GitHub Actions, build hooks, unattended CI rendering or a supported video-generation CLI. Do not treat desktop batch builds as CI integration.

How to use it

For documented batch work, queue video ideas in the desktop app and start or schedule a batch there. A batch is not a CI pipeline, and the computer must stay awake while it runs.

• What desktop batch builds do

Where it helps

If automated pipeline generation is a requirement, confirm support directly with DemoVexa before planning around it. Current documentation describes a local, user-reviewed desktop workflow.

• What's new
• Feature announcement

A practical example

If an organization requires unattended generation on every merge, this page's documented answer is that such CI automation is not documented; a person can schedule desktop batches instead.

What to check before sharing

Do not treat batch builds, local CLI startup or GitHub repository cloning as a CI integration.

Compare the final video with the current product, confirm the selected plan and provider limits, and review the preview at each format before export.

Plan a small, verifiable first use

Start with one outcome this feature should help you prepare, and decide who will judge whether it is ready. Gather only the current product context the task needs: the relevant local app folder or guide, the intended audience, and any voice, brand or format choice that affects the result. Use fictional data and keep credentials, private customer details and unreleased claims out of the brief.

Build a short representative example before preparing a larger set. Review the source and settings, then compare the script and scenes with the product behavior they describe. If the feature depends on a provider, language, plan or destination, state that dependency plainly so the reviewer can judge the right version of the output.

Review changes and pass the files along

When the first preview is ready, check the result in context: listen to the full narration, inspect captions against the audio, and preview each selected aspect ratio. Ask the product owner to verify behavior and labels; ask the publishing owner to check readability, duration and destination requirements. A successful setting or generated draft does not itself confirm that the video is accurate or ready to publish.

For handoff, include the approved MP4, subtitle files when available, the intended placement and the product version used. Keep a reviewer and review date with the asset. Revisit it when the underlying product, provider options or publishing requirements change, then rebuild and review the affected output before replacing an existing video.

Decide whether this feature fits the job

Use this workflow when a reviewed, animated explanation is useful and your team can check it against current product context. If the viewer needs to see a live-only behavior, a real person demonstrating hardware, or an interactive path they can explore themselves, consider whether a screen recording, live demonstration or interactive guide would answer the question more directly. Choose based on what the audience needs to observe.

For this feature, define a simple acceptance check before production: name the visible output that must be present and one condition that would make the draft unsuitable. That could be a required caption track, a verified provider voice, a readable mobile composition or a release-approved screen. Share that check with reviewers so feedback leads to a clear edit or approval decision.