pr

name	pr
description	Open a pull request for the current feature

Ensure we are not on the main branch, make a branch if necessary.
Check whether a PR already exists for the current branch with gh pr status or gh pr view. If one exists, update it with local changes.

If the changes add a Remotion Element, read the Element contribution guide before continuing.

Run Oxfmt on the files or package directories affected by the current change. Pass their actual paths; do not assume that the repository root has a src directory. Include relevant root-level files, and do not format unrelated packages or the whole repository.

For example:

bunx oxfmt <changed-file-or-package-directory>... --write

If none of the changed files are supported by Oxfmt, skip this step. Inspect any formatter changes before committing.

Then run

bun run build
bun run stylecheck

to ensure we compile and CI linting/formatting passes.

Commit the changes once. The title of the PR must be according to the pr-name skill.

Push the changes to the remote branch once, using git push -u origin HEAD.

Never force push, unless users asks for it.

Use the gh CLI to create a pull request and use the same format as above for the title.

When creating the PR, do not pass the PR body inline through a shell command (for example, avoid --body "..." or heredocs in bash). Instead:

1. Write the PR body to a temporary Markdown file in the system temp directory (for example /tmp/remotion-pr-body.md, or a unique file created under /tmp).