chore(pkg): basic setup of repo

basic setup of repo

gh-4

Author: Sunny Tyagi

.cz-config.js

@@ -0,0 +1,67 @@
+module.exports = {
+  types: [
+    {value: 'feat', name: 'feat:     A new feature'},
+    {value: 'fix', name: 'fix:      A bug fix'},
+    {value: 'docs', name: 'docs:     Documentation only changes'},
+    {
+      value: 'style',
+      name: 'style:    Changes that do not affect the meaning of the code\n            (white-space, formatting, missing semi-colons, etc)',
+    },
+    {
+      value: 'refactor',
+      name: 'refactor: A code change that neither fixes a bug nor adds a feature',
+    },
+    {
+      value: 'perf',
+      name: 'perf:     A code change that improves performance',
+    },
+    {value: 'test', name: 'test:     Adding missing tests'},
+    {
+      value: 'chore',
+      name: 'chore:    Changes to the build process or auxiliary tools\n            and libraries such as documentation generation',
+    },
+    {value: 'revert', name: 'revert:   Reverting a commit'},
+    {value: 'WIP', name: 'WIP:      Work in progress'},
+  ],
+
+  scopes: [
+    {name: 'chore'},
+    {name: 'deps'},
+    {name: 'ci-cd'},
+    {name: 'component'},
+    {name: 'provider'},
+    {name: 'core'},
+    {name: 'maintenance'},
+    {name: 'sqs'},
+    {name: 'event-bridge'},
+    {name: 'bullmq'},
+    {name: 'pkg'},
+  ],
+
+  appendBranchNameToCommitMessage: true,
+  appendIssueFromBranchName: true,
+  allowTicketNumber: false,
+  isTicketNumberRequired: false,
+
+  // override the messages, defaults are as follows
+  messages: {
+    type: "Select the type of change that you're committing:",
+    scope: 'Denote the SCOPE of this change:',
+    // used if allowCustomScopes is true
+    customScope: 'Denote the SCOPE of this change:',
+    subject: 'Write a SHORT, IMPERATIVE tense description of the change:\n',
+    body: 'Provide a LONGER description of the change (mandatory). Use "\\n" to break new line:\n',
+    breaking: 'List any BREAKING CHANGES (optional):\n',
+    footer: 'List any ISSUES CLOSED by this change (optional). E.g.: GH-144:\n',
+    confirmCommit: 'Are you sure you want to proceed with the commit above?',
+  },
+
+  allowCustomScopes: false,
+  allowBreakingChanges: ['feat', 'fix'],
+
+  // limit subject length
+  subjectLimit: 100,
+  breaklineChar: '|', // It is supported for fields body and footer.
+  footerPrefix: '',
+  askForBreakingChangeFirst: true, // default is false
+};

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when
+an individual is representing the project or its community in public spaces.
+Examples of representing a project or community include using an official
+project e-mail address, posting via an official social media account, or acting
+as an appointed representative at an online or offline event. Representation of
+a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at support@sourcefuse.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

.github/CONTRIBUTING.md

@@ -0,0 +1,60 @@
+# loopback4-message-bus-queue-connector
+
+## Contributing
+
+First off, thank you for considering contributing to the project. It's people like you that helps in keeping this extension useful.
+
+### Where do I go from here?
+
+If you've noticed a bug or have a question, [search the issue tracker](https://github.com/sourcefuse/loopback4-message-bus-queue-connector/issues) to see if
+someone else in the community has already created a ticket. If not, go ahead and
+[make one](https://github.com/sourcefuse/loopback4-message-bus-queue-connector/issues/new/choose)!
+
+### Fork & create a branch
+
+If this is something you think you can fix, then [fork](https://help.github.com/articles/fork-a-repo) this repo and
+create a branch with a descriptive name.
+
+A good branch name would be (where issue #325 is the ticket you're working on):
+
+```sh
+git checkout -b 325-add-new-feature
+```
+
+### Make a Pull Request
+
+At this point, you should switch back to your master branch and make sure it's
+up to date with loopback4-message-bus-queue-connector's master branch:
+
+```sh
+git remote add upstream git@github.com:sourcefuse/loopback4-message-bus-queue-connector.git
+git checkout master
+git pull upstream master
+```
+
+Then update your feature branch from your local copy of master, and push it!
+
+```sh
+git checkout 325-add-new-feature
+git rebase master
+git push --set-upstream origin 325-add-new-feature
+```
+
+Finally, go to GitHub and [make a Pull Request](https://help.github.com/articles/creating-a-pull-request).
+
+### Keeping your Pull Request updated
+
+If a maintainer asks you to "rebase" your PR, they're saying that a lot of code
+has changed, and that you need to update your branch so it's easier to merge.
+
+To learn more about rebasing in Git, there are a lot of [good][git rebasing]
+[resources][interactive rebase] but here's the suggested workflow:
+
+```sh
+git checkout 325-add-new-feature
+git pull --rebase upstream master
+git push --force-with-lease 325-add-new-feature
+```
+
+[git rebasing]: http://git-scm.com/book/en/Git-Branching-Rebasing
+[interactive rebase]: https://help.github.com/articles/interactive-rebase

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,27 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/stale.yml

@@ -0,0 +1,34 @@
+# Label to use when marking an issue or a PR as stale
+staleLabel: stale
+
+# Configuration for issues
+issues:
+  # Number of days of inactivity before an issue becomes stale
+  daysUntilStale: 90
+  # Comment to post when marking an issue as stale. Set to `false` to disable
+  markComment: >
+    This issue has been marked stale because it has not seen any activity within
+    three months. If you believe this to be an error, please contact one of the code owners.
+    This issue will be closed within 15 days of being stale.
+  # Number of days of inactivity before a stale issue is closed
+  daysUntilClose: 15
+  # Comment to post when closing a stale issue. Set to `false` to disable
+  closeComment: >
+    This issue has been closed due to continued inactivity. Thank you for your understanding.
+    If you believe this to be in error, please contact one of the code owners.
+# Configuration for pull requests
+pulls:
+  # Number of days of inactivity before a PR becomes stale
+  daysUntilStale: 60
+  # Comment to post when marking a PR as stale. Set to `false` to disable
+  markComment: >
+    This pull request has been marked stale because it has not seen any activity
+    within two months. It will be closed within 15 days of being stale
+    unless there is new activity.
+  # Number of days of inactivity before a stale PR is closed
+  daysUntilClose: 15
+  # Comment to post when closing a stale issue. Set to `false` to disable
+  closeComment: >
+    This pull request has been closed due to continued inactivity. If you are
+    interested in finishing the proposed changes, then feel free to re-open
+    this pull request or open a new one.

.github/workflows/build-image.yaml

@@ -16,18 +16,13 @@ jobs:
       - uses: actions/checkout@v3
       - uses: actions/setup-node@v3
         with:
-          node-version: ${{ matrix.node-version }}
+          node-version: '^20.x'
+
       - name: Install Monorepo Deps
         run: npm ci
+
       - name: Run Test Cases
-        run: npm run test --workspaces --if-present
-      - name: Run Lint Checks
-        run: npm run lint --workspaces --if-present
+        run: npm run test
 
-  npm_test:  
-    runs-on: ubuntu-latest
-    needs: node_matrix_tests
-    if: success()
-    steps:
-      - name: Final status
-        run: echo "✅ All tests passed for Node.js 20, 22, and 24"
+      - name: Run Lint Checks
+        run: npm run lint