submit-to-extension-index

Submitting a 3D Slicer extension involves validating your extension, forking the index repository, creating a branch, copying your extension JSON, and opening a pull request. This workflow automates those steps to ensure validation and clean submission history.

Yes, you can validate your 3D Slicer extension before opening a pull request. The workflow runs a pre-submission validator to catch issues early, ensuring your extension meets the Extension Index requirements before you proceed with forking and branch creation.

The process for forking and cloning the Slicer extension index repository is guided step-by-step. It handles forking the repository, cloning it locally, and creating a branch to maintain a clean submission history before you copy your extension JSON and push.

To create a pull request for a 3D Slicer extension submission, the workflow pre-populates the PR body using the latest template. This streamlines code review by ensuring all required information is included after you push your extension branch to the forked repository.

Yes, you need git to automate your 3D Slicer extension submission. The workflow relies on git operations like forking, cloning, branch creation, and pushing to manage the end-to-end submission steps and maintain a clean submission history in the Extension Index.