JamesandClaude Opus 4.6
bce1a11e71
The 3-workflow chain (release.yml → release-tag.yml → publish.yml) was broken by design: tags created by GITHUB_TOKEN don't trigger other workflows, so merging a release PR never actually published. Consolidate into a single publish.yml that triggers on both tag push and release PR merge. Delete the redundant prepare-release and tag-release workflows. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
4.1 KiB
Contributing to Hyperframes
Thanks for your interest in contributing to Hyperframes! This guide will help you get started.
Getting Started
- Fork the repository
- Clone your fork:
git clone https://github.com/YOUR_USERNAME/hyperframes.git - Install dependencies:
bun install - Create a branch:
git checkout -b my-feature
Development
bun install # Install all dependencies
bun run dev # Run the studio (composition editor)
bun run build # Build all packages
bun run --filter '*' typecheck # Type-check all packages
bun run lint # Lint all packages
bun run format:check # Check formatting
Running Tests
bun run --filter @hyperframes/core test # Core unit tests (vitest)
bun run --filter @hyperframes/engine test # Engine unit tests (vitest)
bun run --filter @hyperframes/core test:hyperframe-runtime-ci # Runtime contract tests
Linting & Formatting
bun run lint # Run oxlint
bun run lint:fix # Run oxlint with auto-fix
bun run format # Format all files with oxfmt
bun run format:check # Check formatting without writing
Git hooks (via lefthook) run automatically after bun install and enforce linting + formatting on staged files before each commit.
Pull Requests
- Use conventional commit format for all commits (e.g.,
feat: add timeline export,fix: resolve seek overflow). Enforced by a git hook. - CI must pass before merge (build, typecheck, tests, semantic PR title)
- PRs require at least 1 approval
Packages
| Package | Description |
|---|---|
@hyperframes/core |
Types, HTML generation, runtime, linter |
@hyperframes/engine |
Seekable page-to-video capture engine |
@hyperframes/producer |
Full rendering pipeline (capture + encode) |
@hyperframes/studio |
Composition editor UI |
hyperframes |
CLI for creating, previewing, and rendering |
Releasing (Maintainers)
All packages use fixed versioning — every release bumps all packages to the same version.
bun run set-version 0.2.0
git checkout -b release/v0.2.0
git add packages/*/package.json
git commit -m "chore: release v0.2.0"
git push origin release/v0.2.0
gh pr create --title "chore: release v0.2.0" --base main
# After merge, tag + npm publish + GitHub Release happen automatically
You can also publish manually by pushing a tag: git tag v0.2.0 && git push origin v0.2.0
Reporting Issues
- Use GitHub Issues for bug reports and feature requests
- Search existing issues before creating a new one
- Include reproduction steps for bugs
AI-Assisted Contributions
We welcome contributions that use AI tools (GitHub Copilot, Claude, ChatGPT, etc.). If you used AI to help write a PR, there is no need to disclose it — we review all code on its merits. However:
- You are responsible for the correctness of any code you submit, regardless of how it was generated.
- AI-generated tests must actually test meaningful behavior, not just assert truthy values.
- Do not submit AI-generated code you don't understand. If you can't explain what a change does during review, it will be rejected.
Governance
Hyperframes uses a BDFL (Benevolent Dictator for Life) governance model. The core maintainers at HeyGen have final say on the project's direction, API design, and what gets merged. This keeps the project focused and moving fast.
Community input is valued and encouraged — open issues, propose RFCs, and discuss in PRs. But final decisions rest with the maintainers.
Code of Conduct
This project follows the Contributor Covenant Code of Conduct. By participating, you are expected to uphold this code.
License
By contributing, you agree that your contributions will be licensed under the project's license. See LICENSE for details.