- Fork this repo and clone the forked on your local environment
- Run
npm install
to install all dependencies- Run
npx husky install
to enable commit hooks
- Run
- Start working on changes
_docs-site
_packages
\_classes
\_core
\_integration-test
\_nestjs
\_nestjs-integration-test
\_pojos
\_types
docs-site
: This is the documentations site powered by Docusaurus.classes
:classes
plugincore
:core
packagenestjs
:nestjs
integrationpojos
:pojos
plugintypes
: type definitionsintegration-test
/nestjs-integration-test
: tests for both plugins andnestjs
integration
- Run
npm run test:all
to run all test suites.
After you finish with the changes
- Run
git add .
to stage all changes - Run
npm run commit
to start Conventional Commit flow- Pick one of the type of changes from the options: feat, fix, chore, docs etc...
- If you modify changes in
core
,classes
,nestjs
,pojos
, ortypes
, please include at least one of this as thescope
. Eg:feat(classes)
, orfix(core)
etc...
@automapper/*
follows SemVer (major.minor.patch
versioning) and utilizes release-it
to semi-automate the release process. The next version will be based on the type of changes from the commits
feat
will issue aminor
version bump. Eg:1.0.0
->1.1.0
fix
,perf
, andrefactor
will issue apatch
version bump. Eg:1.0.0
->1.0.1
- When asked about BREAKING CHANGES during the Conventional Commit flow, the
major
version will be bumped if you answer YES. Eg:1.0.0
->2.0.0
CHANGELOG
will be generated automatically by release-it
based on the commits' messages. If you want to be thorough, please include some description of your changes in the PR so that I can manually add that to the CHANGELOG
when we cut a new release.
pre-commit
hook will run some linting and formatting. Depending on the amount of changes, this might take a while.
When ready, please submit a PR.