Monorepo (via π¦ pnpm and πΊ turbo) for tools I use frequently in various projects, people, and companies I work with.
@jeromefitz/tsconfig@jeromefitz/oxlint-config(local only, not published)
ccommit: conventional commit generator that interprets commit types fromgitmojithroughconventional-commits@jeromefitz/conventional-gitmoji: Mapsgitmojitoconventional-commitsw/ semver recognition:feat => β¨οΈfix => ποΈci => π·οΈfix-ci => ποΈ...
@jeromefitz/semantic: Automatic Semantic Versioning throughsemantic-releasewith support forgitmoji.@jeromefitz/release-notes-generator: You guessed it, a custom release-notes-generator- This does not use
handlebarsbasically. - π See the latest output at the releases page.
- This does not use
@jeromefitz/notion- ποΈ API (hyper-customized
@notionhq/client) forNotion - ποΈ Live Example:
jeromefitzgerald.com - π
next-notion
- ποΈ API (hyper-customized
- π
@jeromefitz/scripts- π scripts that are used to set up repos and for CI/CD
- π§°οΈ
@jeromefitz/utils- Scripts that are generically re-used throughout
@jeromefitz/dotfiles: Separate from this repository- zsh + homebrew computer setup
@jeromefitz/codestyle@jeromefitz/design-system@jeromefitz/eslint-config@jeromefitz/git-cz@jeromefitz/jest-config@jeromefitz/jest-presets@jeromefitz/lighthouse-config@jeromefitz/lint-staged@jeromefitz/prettier-config@jeromefitz/spotify
- π¦
pnpm workspaces - π
GitHub Actionsfor CI/CD- Plus release management through npm
- πΊοΈ
turbofor monorepo management- cache: local / remote & team development
- cache: github actions
- π·οΈ
tsdownfor typescript builds (w/ some config) - π€οΈ
Renovatefor Patch + Minor Package Management - π€οΈ
Kodiakto βAutomate (our) GitHub Pull Requestsβ - π€οΈ Automatic
Semantic Versioningw/Conventional Commits- ποΈ Commits & Versioning (Release Notes) made more fun by a few of the packages in this repo
pull: PRs intomainpush:main+ Ability forx.y.z-canary.#builds via:./release.config.jsweekly: Ifmaindid not trigger a build (Renovate/[skip ci]) check to see if it should
If you would like to opt-out of the git hooks please look at .env.example.
Normally, these would be opt-in and may change to that in the future.