Video source collaboration guide

Use your existing MotionGit account to collaborate on a complete video project. The template center handles previews, licensing and downloads; the source site handles code, forks, proposals and review.

01 · Find a project that allows collaboration

Start in the template center. Check the video and its license, then open source collaboration. A public repository is not automatically a published template, and a personal fork does not inherit marketplace release status.

Linked repositories offer “Preview & download” and “Release provenance”. The displayed marketplace version may differ from the current branch or commit. Forks explicitly label these links as upstream.

02 · Make changes in your own fork

  1. Your MotionGit account works across both sites. Open a repository to continue collaborating.
  2. Read the README, guide.json, parameter contract and licenses/. Check permission to modify, derive and redistribute source and assets.
  3. Fork the repository, create a branch in your copy, edit the content or animation, and commit the changes.

Public repositories allow anonymous cloning. Configure Git access credentials in the source site’s account settings for pushing. Browser login and command-line Git authentication are separate usage contexts; an email verification code is not a Git password.

Import original source before any personal Key is injected. Exclude motiongit.key.json, credentials, private voiceovers, subtitles, finished videos, node_modules and other dependency caches.

03 · Propose the next version with a PR

  1. Open “Proposals (PR)” in the upstream repository. Create a pull request and select your branch and the upstream target branch.
  2. Explain what changed, why, how you tested it, and whether assets or licensing changed. Do not upload private assets as review attachments.
  3. The maintainer checks source diffs, static-check results and review comments before merging. Native permissions and required checks still apply.

A proposal is a Git pull request. Source diffs are available; synchronized video comparison, frame-level provenance and frame-level review are not available yet.

04 · Build and submit a separate marketplace release

  1. The maintainer selects a pinned commit already in the default branch and uses the verified builder to create .motion and its provenance receipt.
  2. Inspect the project and verify the commit SHA, original package SHA256 and integrity fingerprint separately, then use the main site’s existing release process.
  3. Only versions that pass checks and release review appear in the template center for preview and download.

Merging a PR does not publish a template. Git releases and tags are not marketplace versions. The source site does not execute projects or offer one-click cloud rendering.

Open the publishing page → · Read the .motion specification →

05 · Know where to go when a status is unavailable

  • If template summaries cannot load, native source browsing, forks and PRs continue as usual. Missing template links do not prove a project is unpublished.
  • Updating or retrying notices mean the summary may be delayed. The main site’s provenance record is authoritative.
  • If Git is temporarily unavailable, published templates remain available to browse and download in the template center.

For advanced Git branches, merge strategies and account settings, see the official Gitea documentation.