[HOT FIX 1E | NO-TICKET] Change central CI name

.github/workflows/central-node-ci.yml → .github/workflows/central-blocks-ci.yml

@@ -1,4 +1,4 @@
-name: Central Node CI Quality Check
+name: Central Blocks CI
 on:
   # --------------------------------------------------------------------
   # 1. This lets user apps that use dev.setup library call this workflow

README.md

@@ -188,7 +188,7 @@ npm install -D @build-in-blocks/dev.setup
       # -----------------------------------------------------------------
       # This points to the shared library repository's "central" workflow
       # -----------------------------------------------------------------
-      uses: build-in-blocks/dev.setup/.github/workflows/central-node-ci.yml@v1.0.1
+      uses: build-in-blocks/dev.setup/.github/workflows/central-blocks-ci.yml@v1.0.1
       with:
         run_tests: true
         # -------------------------------------------------
@@ -197,7 +197,7 @@ npm install -D @build-in-blocks/dev.setup
         extra_scripts: ""
   ````
   > [!IMPORTANT]  
-  > Make sure the version used in the .yml file's `call-shared-logic` in `uses: build-in-blocks/dev.setup/.github/workflows/central-node-ci.yml@v[VERSION_NUMBER_HERE]`, is the same as the version of the `@build-in-blocks/dev.setup` package in your `package.json` file.
+  > Make sure the version used in the .yml file's `call-shared-logic` in `uses: build-in-blocks/dev.setup/.github/workflows/central-blocks-ci.yml@v[VERSION_NUMBER_HERE]`, is the same as the version of the `@build-in-blocks/dev.setup` package in your `package.json` file.
 
  - Add the scripts you'd like to run in `extra_scripts` e.g. if you'd like the CI to run `build` and `e2e` npm scripts from your `package.json` file, update the extra_scripts like so:
 

docs.users/README.md

@@ -68,7 +68,7 @@ In addition to `prettier`'s default settings, our preconfigured settings tells `
 > Let your linting script name remain as `eslint:lint` in the script section of your `package.json`. This way, the CI running on your pull requests, on push and on merge, will be able to detect your lint script and run it.
 
 > [!NOTE]  
-> The supported `Node.js` versions for installing and running your project, is the same as the what's on our package's [root README.md](https://github.com/build-in-blocks/dev.setup). Our `central-node-ci.yml` however, runs a wider range of `Node.js` versions (You'll notice this on the CI that runs on your project repository's pull requests, on push and on merge) - which is how we are able to detect the supported `Node.js` versions for both our package and your project.
+> The supported `Node.js` versions for installing and running your project, is the same as the what's on our package's [root README.md](https://github.com/build-in-blocks/dev.setup). Our `central-blocks-ci.yml` however, runs a wider range of `Node.js` versions (You'll notice this on the CI that runs on your project repository's pull requests, on push and on merge) - which is how we are able to detect the supported `Node.js` versions for both our package and your project.
 
 - The GitHub Actions CI runs these `npm` scripts in your project by default: `install` and `eslint:lint`.
 - See [root README.md](https://github.com/build-in-blocks/dev.setup) for how to add other `npm` scripts that you have in your project, and that you want GitHub Actions to run too.