Update CI/CD process

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,59 @@
+<!--
+     For Work In Progress Pull Requests, please use the Draft PR feature,
+     see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details.
+
+     For a timely review/response, please avoid force-pushing additional
+     commits if your PR already received reviews or comments.
+
+     Before submitting a Pull Request, please ensure you've done the following:
+     - 📖 Read the Code of Conduct: https://github.com/lean-mind/monads/blob/main/CODE_OF_CONDUCT.md
+     - 👷‍♀️ Create small PRs. In most cases this will be possible.
+     - ✅ Provide tests for your changes.
+     - 📝 Use descriptive commit messages.
+     - 📗 Update any related documentation and include any relevant screenshots.
+
+     NOTE: Pull Requests from forked repositories will need to be reviewed by
+     a Forem Team member before any CI builds will run. Once your PR is approved
+     with a `/ci` reply to the PR, it will be allowed to run subsequent builds without
+     manual approval.
+-->
+
+## What type of PR is this? (check all applicable)
+
+- [ ] Refactor
+- [ ] Feature
+- [ ] Bug Fix
+- [ ] Optimization
+- [ ] Documentation Update
+
+## Description
+
+<!-- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and
+context. List any dependencies that are required for this change. -->
+
+## Related Tickets & Documents
+
+<!--
+For pull requests that relate or close an issue, please include them
+below.  We like to follow [Github's guidance on linking issues to pull requests](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue).
+
+For example having the text: "closes #1234" would connect the current pull
+request to issue 1234.  And when we merge the pull request, Github will
+automatically close the issue.
+-->
+
+- Related Issue #
+- Closes #
+
+## Added/updated tests?
+
+_We encourage you to keep the quality of the code by creating test._
+
+- [ ] Yes
+- [ ] No, and this is why: _please replace this line with details on why tests
+  have not been included_
+- [ ] I need help with writing tests
+
+## [optional] What gif best describes this PR or how it makes you feel?
+
+![alt_text](gif_link)

.github/workflows/node.js.yml → .github/workflows/ci.yml

@@ -1,4 +1,4 @@
-name: Node.js CI
+name: CI
 
 on:
   push:
@@ -19,6 +19,13 @@ jobs:
         with:
           node-version: ${{ matrix.node-version }}
           cache: "npm"
-      - run: npm ci
-      - run: npm run build
-      - run: npm test
+      - name: CI Setup
+        run: npm ci
+      - name: Code Quality Checks
+        run: |
+          npm run lint
+          npm run format:check
+      - name: Build
+        run: npm run build
+      - name: Test
+        run: npm test

.github/workflows/release.yml

@@ -19,8 +19,16 @@ jobs:
       - uses: actions/setup-node@v4
         with:
           node-version: "lts/*"
-      - run: npm ci
-      - run: npm run build
+      - name: CI Setup
+        run: npm ci
+      - name: Code Quality Checks
+        run: |
+          npm run lint
+          npm run format:check
+      - name: Build
+        run: npm run build
+      - name: Test
+        run: npm test
       - run: npm audit signatures
       - name: Release
         env:

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leanmind/monads",
-  "version": "0.0.0",
+  "version": "0.0.0-semantically-released",
   "description": "A collection of monads implemented in TypeScript using object-oriented programming.",
   "keywords": [
     "functional-programming",
@@ -19,6 +19,7 @@
     "lint:watch": "esw --color --watch",
     "lint:fix": "npm run lint -- --fix",
     "format": "prettier --config .prettierrc '**/*.+(ts|tsx)'",
+    "format:check": "npm run format -- --check",
     "format:fix": "npm run format -- --write",
     "test": "vitest run",
     "semantic-release": "semantic-release"

release.config.cjs

@@ -1,3 +1,6 @@
+/**
+ * @type {import('semantic-release').GlobalConfig}
+ */
 module.exports = {
   branches: ['main', { name: 'beta', prerelease: true }],
 };