git-ci

Create a workflow file that runs typecheck, lint, test, and build as separate jobs on pushes and pull requests to main. Use actions/checkout with oven-sh/setup-bun or actions/setup-node, install dependencies with a frozen lockfile, and make the build job depend on the other checks passing.

Conventional Commits use a type(scope): subject format like feat(auth): add OAuth2 provider, with types including feat, fix, docs, refactor, and chore. Enforce them with commitlint wired into a Husky commit-msg git hook so non-conforming messages are rejected.

Use the release-please GitHub Action on pushes to main, which parses conventional commits to determine semantic version bumps and generates changelogs. It opens a release PR that, when merged, tags the version and publishes the release.

Yes, but branches must be short-lived (under two days) and merged daily into a protected main branch. Use feature flags for incomplete work and delete branches after merging to keep main always deployable.

Add a dependabot.yml file specifying the npm ecosystem, weekly schedule, and groups that separate development and production dependencies into batched pull requests. Assign reviewers and labels so updates route to the right maintainers.