Introducing a new way to review your PRs.

Read the announcement

opencut-app / opencut

The open-source CapCut alternative

View on GitHub

12 documents · Updated Nov 16, 2026

docs / ci-release-flows


slug: docs/ci-release-flows.md covers:

  • .github/workflows/**
  • .github/pull_request_template.md
  • .github/ISSUE_TEMPLATE/**
  • .github/CODE_OF_CONDUCT.md
  • .github/SECURITY.md
  • .github/SUPPORT.md

CI and release flows

Overview

This area defines repository automation and contributor-facing policies that shape CI, release, issue triage, and review intake. The always-on CI entry point is .github/…/bun-ci.yml: it runs on push to main and on pull requests targeting main, except when the change only matches root-level *.md paths. A concurrency group keyed by github.ref cancels older in-progress runs for the same branch or pull request ref. The single ci job fans out across ubuntu-latest, windows-latest, and macos-latest, checks out the full git history with fetch-depth: 0, installs the repository toolchain through moonrepo/setup-toolchain@v0 with auto-install and auto-setup enabled, then runs moon ci.

The release-like automation is manual and scoped to media dependencies in .github/…/media-deps.yml. It is triggered only through workflow_dispatch and requires a build input used to distinguish rebuilds of the same FFmpeg version. The build job reads the FFmpeg version from crates/…/ffmpeg.json and the Bun version from .prototools, installs Bun, then builds FFmpeg artifacts by running bun run crates/media/setup/setup.ts --from-source --target ${{ matrix.platform }}. The matrix produces archives for Linux x86_64/aarch64, Windows x86_64/aarch64, and macOS x86_64/aarch64; Windows builds cross-compile from Linux using a pinned llvm-mingw tarball and SHA-256, while x86_64 Linux and macOS builds install nasm. Each matrix leg packages .cache/media/ffmpeg-<version>-<platform> as ffmpeg-*.tar.gz and uploads it as an artifact. The downstream release job downloads all artifacts, computes checksums.sha256, and uses gh release create with the repository token to publish a prerelease tag named ffmpeg-<version>-<build> against the workflow commit. The release notes tell maintainers to pin those assets with bun run crates/media/setup/pin.ts <tag>.

Review intake is intentionally restrictive. .github/pull_request_template.md tells contributors that pull requests are not currently accepted except for critical bugs; bug-fix PRs should have an issue opened first and maintainer approval, while feature PRs should be discussed in an issue and may be closed. Issue intake is split between .github/…/bug_report.yml and .github/…/feature_request.yml. Bug reports require platform, browser, current behavior, recurrence probability, and reproduction steps, with expected behavior and additional context optional. Feature requests receive the enhancement label and require problem, solution, and alternatives fields before optional context.

Support and conduct policy files define where users should route non-code activity. .github/SUPPORT.md directs setup questions to the README and contributing guidelines, bugs and feature ideas to the issue templates, and general questions to GitHub Discussions; it also states expected triage timing and that security issues receive priority. .github/SECURITY.md declares support for version 1.x.x, asks reporters to email security@opencut.app instead of opening public GitHub issues, and lists report contents plus acknowledgement and response timelines. .github/CODE_OF_CONDUCT.md is based on Contributor Covenant 2.1 and applies moderation expectations to issues, comments, commits, wiki edits, and other contributions, with reports routed to the project's Discord server.

Coupling

  • If .github/…/bun-ci.yml changes its toolchain setup or moon ci invocation, verify the repository still has compatible Moon/Bun configuration because CI delegates all actual validation to moon ci after moonrepo/setup-toolchain@v0.
  • If .prototools or the FFmpeg pin schema in crates/…/ffmpeg.json changes, update .github/…/media-deps.yml; it parses both files with shell commands before setup, packaging, and release tagging.
  • If crates/…/setup.ts changes its target names or output directory layout, verify .github/…/media-deps.yml still passes valid ${{ matrix.platform }} values and can package .cache/media/ffmpeg-<version>-<platform> without silently uploading the wrong archive name.
  • If the repository starts accepting broader external contributions, update .github/pull_request_template.md, .github/SUPPORT.md, and the issue templates together so PR guidance, support routing, and triage expectations do not contradict each other.
  • If security reporting ownership changes, update both .github/SECURITY.md and .github/SUPPORT.md; support policy says security issues receive priority, while the security policy is the only file that gives the private reporting address and timeline.

Risks

  • .github/…/bun-ci.yml ignores root-level Markdown-only changes with paths-ignore: "*.md". If repository behavior depends on root Markdown instructions, examples, or policy files, those changes will not run CI.
  • .github/…/media-deps.yml has permissions: contents: write and publishes prerelease assets with gh release create. If the workflow is manually dispatched with the wrong build value or from the wrong commit, it can create an authoritative FFmpeg prerelease tag pointing at an unintended source revision.
  • .github/…/media-deps.yml hard-codes the llvm-mingw version, download URL, and SHA-256. If the upstream asset disappears or the checksum no longer matches the expected tarball, both Windows matrix legs fail before the release job can publish a complete artifact set.