video-artifact-publish

You can publish video artifacts with traceable links by automating the collection of rendered outputs and uploading them via actions/upload-artifact@v4, which generates an accessible run URL, artifact name, and video path for your issue comments.

To collect Manim video outputs for CI/CD traceability, the workflow gathers rendered files from outputs/manim/** and media/videos/** directories, uploading them as verifiable artifacts with explicit retention days.

Yes, actions/upload-artifact@v4 supports traceability by enabling a workflow that posts a final issue comment containing the run URL, artifact name, video path, and source URLs for script content.

The best way to share rendered video outputs is to package them as GitHub Actions artifacts, ensuring they are stored with accessible run links and verifiable sources for reproducibility and easy sharing.

Yes, you can use this artifact publishing workflow for non-Manim pipelines as long as your rendered video outputs are collected from the expected outputs/manim/** and media/videos/** directory paths.

Including run URLs and source URLs when uploading video artifacts ensures reproducibility and easy sharing by providing verifiable sources and accessible links directly in the final issue comment.