A reusable Autodesk Fusion add-in starter for 4FusionLab. It includes a working command, a Fusion manifest, offline tests, cross-platform CI, deterministic ZIP packaging and the shared 4FusionLab automatic release policy.
- Click Use this template → Create a new repository, preferably in the
4FusionLaborganization. - In the new repository open Actions → Initialize add-in → Run workflow. The repository name becomes the Python add-in package name; you can enter a friendly display name and description.
- The initialization commit generates a new manifest UUID and command ID, renames the add-in package and prepares the bilingual project README files.
- Develop your add-in in its package directory. Run
python -m unittest discover -s tests -vandpython scripts/build.py --version 0.1.0for a local verification. - After initialization, every push or merged PR to
mainwhich touches shipped runtime files is eligible for an automatic release, subject to green CI. Documentation and test-only changes do not publish.
If Actions cannot be enabled yet, run the initializer locally: python scripts/init_addin.py --name MyNewAddin --display-name "My New Add-in", commit its changes and push.
Never install or publish the uninitialized
FusionAddinplaceholder as a real product.
- GitVersion.Tool 6.8.2 and conventional commit conventions.
- Immutable, SHA-pinned composite Actions from 4FusionLab/.github.
- CI on Linux, macOS and Windows; offline tests are distinct from real Fusion acceptance.
- ZIP and SHA-256 verification; no manually created release tags.
- Separate English and Russian documentation and
AGENTS.mdrules for coding agents.
The repository is a template, not an existing 4FusionLab product. See docs/DEVELOPMENT.md after scaffolding is installed.
The initializer creates starter pages, not finished product documentation. Before publishing a product, replace the starter description in both README.md and README.ru.md with accurate, separately written English and Russian text. Follow the product README guidelines: explain the user outcome and actual workflow, link real releases and support, give install steps, and state important limitations and verified platform status. Include safety warnings prominently when relevant; preserve existing examples and assets. Check links, language parity and the current license before delivery. Write documentation in English with a separate Russian version; intermediate working notes do not require translation.