Added contrib related files.

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,42 @@
+name: Bug Report
+description: File a bug report
+title: "[Bug]: "
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+  - type: dropdown
+    id: microservices
+    attributes:
+      label: Which microservice are you seeing the problem on?
+      multiple: true
+      options:
+        - Ingestion
+        - DB Server
+        - Frontend
+        - Not Sure
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: Also tell us, what did you expect to happen?
+      placeholder: Tell us what you see!
+      value: "A bug happened!"
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+      render: bash
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/Hyperclaw79/StocksALot/CODE_OF_CONDUCT.md).
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Community Discussions
+    url: https://github.com/Hyperclaw79/StocksALot/discussions
+    about: Please ask and answer questions here.
+  - name: Security Bug Bounty
+    url: https://mailxto.com/6wjdozbi2y
+    about: Please report security vulnerabilities here.
+  - name: Code of Conduct Violation
+    url: https://mailxto.com/n5d13a4ph7
+    about: Please report COC violations here.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,41 @@
+name: Feature Request
+description: Request a new feature
+title: "[Feature Request]: "
+labels: ["enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to request a new feature!
+  - type: textarea
+    id: what-feature
+    attributes:
+      label: What feature would you like to request?
+      description: Please describe the feature you would like to see added to the project.
+      placeholder: "I would like to see a feature that..."
+    validations:
+      required: true
+  - type: textarea
+    id: why-feature
+    attributes:
+      label: Why do you think this feature would be useful?
+      description: Please explain why you think this feature would be useful to the project.
+      placeholder: "This feature would be useful because..."
+    validations:
+      required: true
+  - type: dropdown
+    id: priority
+    attributes:
+      label: What priority should this feature have?
+      options:
+        - Low
+        - Medium
+        - High
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/Hyperclaw79/StocksALot/CODE_OF_CONDUCT.md).
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,42 @@
+# Description
+
+Please include a summary of the changes and the related issue.\
+Please also include relevant motivation and context.\
+List any dependencies that are required for this change.
+
+Fixes # (issue): ___________ (Leave blank if not applicable)
+
+# Microservices Affected
+
+Which microservices are affected by this change?
+
+- [ ] Frontend
+- [ ] Database
+- [ ] Ingestion
+- [ ] Others (RabbitMQ, Redis, etc.) Please specify: ___________
+
+# Type of change
+
+Please select the relevant options.
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Misc (Test Coverage, Documentation, etc.) Please specify: ___________
+
+# How Has This Been Tested?
+
+Please describe the tests that you ran to verify your changes.
+Provide instructions so we can reproduce.
+
+
+# Checklist:
+
+- [ ] My code follows the style guidelines of this project. Following linters have been run:
+  - [ ] Eslint
+  - [ ] Pylint
+- [ ] I have performed a self-review of my code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] My changes generate no new warnings
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] New and existing unit tests pass locally with my changes

.github/workflows/build.yml

@@ -8,8 +8,13 @@ on:
         branches:
             - main
         paths-ignore:
-            - "README.md"
             - "assets/**"
+            - ".github/**"
+            - "README.md"
+            - "CODE_OF_CONDUCT.md"
+            - "CONTRIBUTING.md"
+            - "LICENSE"
+            - "SECURITY.md"
 
 permissions:
     id-token: write

.github/workflows/cloud-deploy.yml

@@ -7,10 +7,14 @@ on:
         branches:
             - main
         paths-ignore:
-            - "README.md"
             - "assets/**"
             - ".github/**"
             - "!.github/workflows/build.yml"
+            - "README.md"
+            - "CODE_OF_CONDUCT.md"
+            - "CONTRIBUTING.md"
+            - "LICENSE"
+            - "SECURITY.md"
 
 permissions:
     id-token: write

CODE_OF_CONDUCT.md

@@ -0,0 +1,129 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible 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.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders 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, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+harshith.thota7@gmail.com.
+Use the subject line `[StocksALot] Code of Conduct Violation Report`.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

CONTRIBUTING.md

@@ -0,0 +1,47 @@
+# Contributing to [StocksALot]
+
+Thank you for your interest in contributing to this project! Here are some guidelines to help you get started.
+
+## Issues
+
+If you encounter a bug or have a feature request, please use the appropriate issue template to submit an issue.
+
+## Pull Requests
+### Ways to contribute
+Here are some ways in which you can contribute, in ascending order of preference:
+- Report a bug
+- Fix an existing bug
+- Improve test coverage
+- Improve documentation
+- Enhance Frontend
+- Add new features
+- Refactor code
+
+If you would like to contribute code to this project, please follow these steps:
+
+1. Fork the repository
+2. Create a new branch for your changes
+3. Make your changes
+4. Test your changes
+5. Submit a pull request (please make sure to use the pull request template)
+6. Wait for your pull request to be reviewed
+7. Make any requested changes
+8. Wait for your pull request to be merged
+9. Celebrate!
+
+## Code Style
+
+Please follow the existing code style in this project. If you're not sure what that is, take a look at the existing code and try to match it.
+Run the Pylint and Eslint linters to ensure that your code follows the style guidelines.
+
+## Testing
+
+Please make sure your code is thoroughly tested before submitting a pull request. We use unit tests to ensure that the code works as expected.
+
+## Code of Conduct
+
+Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
+
+## License
+
+This project is licensed under the [BSD-3-Clause license](/LICENSE). By contributing to this project, you agree to the terms and conditions of this license.

LICENSE

@@ -0,0 +1,28 @@
+BSD 3-Clause License
+
+Copyright (c) 2023, Harshith Thota
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this
+   list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions and the following disclaimer in the documentation
+   and/or other materials provided with the distribution.
+
+3. Neither the name of the copyright holder nor the names of its
+   contributors may be used to endorse or promote products derived from
+   this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.