Use a local GitHub repository

What it does

DemoVexa can read a cloned repository folder on the same computer. A workspace points to the folder; no GitHub app, hosted repository connection or automatic sync is documented.

How to use it

Clone the repository with your own Git client, pull the branch you plan to show, then select its folder under Workspace settings → App & docs. DemoVexa reads the current local files; pull changes yourself before making a new video.

• Choose and update a local code folder

Where it helps

A local code folder can help a product walkthrough reflect the current checked-out version. Never place secrets or customer data in a video prompt, source examples or sample screens.

• Coding tutorial
• Feature demo
• Technical architecture

A practical example

To explain a changed workflow, a developer can clone the intended branch, select its app folder in the workspace and build from that local state.

What to check before sharing

Verify the branch and folder before building. DemoVexa does not connect to GitHub or follow future pushes automatically.

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.