Home of public scheme for ageras-com organization
- The repository expects conventional commits so release versioning is a automated process.
Releases are generated based on Conventional Commits. When a PR is merged into main
, release-please
creates a PR with release notes and version.
Commits not following Conventional Commits will be ignored. To force a version, push an empty commit:
git commit --allow-empty -m "chore: release 6.1.1" -m "Release-As: v6.1.1"
- config - Configuration schema for NestJS golden path