send-it

Automating your release process requires orchestrating code commits, lint checks, changelog updates, PR creation, and Linear issue transitions together. This workflow ensures code quality and consistent releases by handling each step sequentially, from atomic commits to transitioning issues to 'In Review'.

To update your changelog and transition Linear issues during PR creation, use an automation tool that creates dated changelog entries for every PR and transitions linked Linear issues to 'In Review'. This ensures your documentation and project tracking stay current automatically.

You need the 'git' and 'gh' command-line tools installed, along with the sibling skills 'commit', 'preflight', 'changelog', and 'linear-sync'. These dependencies are required to orchestrate the full release process from code commits to Linear issue transitions.

An all-in-one ship finisher orchestrates the entire release process by automating code commits, change-gated lint preflight, changelog updates, Conventional Commits PR titles, and Linear issue transitions to 'In Review', making your code release process efficient and error-free.

No, this release automation supports both monorepos and single-package repositories. It facilitates consistent and streamlined releases by orchestrating commits, lint preflight checks, changelog updates, and PR creation across different repository structures.

You should not use an automated release workflow if your project lacks the required 'git' and 'gh' command-line tools, or if you do not need automated changelog updates, Conventional Commits PR titles, or Linear issue transitions for your specific release process.