From e971ac28b3638e4588be852e166adbbe6310c38e Mon Sep 17 00:00:00 2001 From: Joseph Garrone Date: Mon, 11 Dec 2023 21:39:09 +0100 Subject: [PATCH] Update README.md --- README.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index b185567..ac9e8b6 100644 --- a/README.md +++ b/README.md @@ -15,14 +15,11 @@ Look no further - ts-ci is here to jumpstart your journey towards becoming a pro Main selling points: - Unlike traditional CLI tools, `ts-ci` utilizes automation within Github Actions. Simply update your `package.json` version number and push. Your new version is automatically published on NPM. -- It offers the convenience of publishing prereleases. All you need to do is update your package version to a prerelease format like `1.2.3-rc.3`. -- It fosters enhanced quality control as it runs tests against the submitter's fork whenever a PR is opened. -- `ts-ci` doesn't bundle your library into a single file. Instead, users can cherry-pick imports from your library, enabling tree shaking. For instance: `import { aSpecificFunction } from "your-module/aSpecificFile"`. - +- It doesn't bundle your library into a single file. Instead, users can cherry-pick imports from your library, enabling tree shaking. For instance: `import { aSpecificFunction } from "your-module/aSpecificFile"`. +- It's just a starting point. It provides a good default CI workflow that you can adapt to your needs. https://user-images.githubusercontent.com/6702424/197344513-065246b9-8823-4894-a9a7-6c539da10655.mp4 - # Examples of project using this template - [Keycloakify](https://github.com/garronej/keycloakify)