Testing for Bot - Ignore

.github/ISSUE TEMPLATE/bug_template.md

@@ -0,0 +1,40 @@
+---
+name: 🐞 Bug
+about: File a bug/issue
+title: '[BUG] <title>'
+labels: Bug, Needs Triage
+assignees: ''
+
+---
+
+<!--
+Note: Please search to see if an issue already exists for the bug you encountered.
+-->
+
+### Current Behavior:
+<!-- A concise description of what you're experiencing. -->
+
+### Expected Behavior:
+<!-- A concise description of what you expected to happen. -->
+
+### Steps To Reproduce:
+<!--
+Example: steps to reproduce the behavior:
+1. In this environment...
+2. With this config...
+3. Run '...'
+4. See error...
+-->
+
+### Environment:
+<!--
+Example:
+- OS: Ubuntu 20.04
+- Node: 13.14.0
+- npm: 7.6.3
+-->
+
+### Anything else:
+<!--
+Links? References? Anything that will give us more context about the issue that you are encountering!
+-->

.github/PULL REQUEST TEMPLATE/pull_request_template.md

@@ -0,0 +1,28 @@
+<!-- Remove this section if not applicable -->
+
+## 🛠️ Fixes Issue
+
+Closes #
+<!-- Example: Closes #31 -->
+
+## 👨‍💻 Changes proposed
+
+<!-- List all the proposed changes in your PR -->
+
+## ✔️ Check List (Check all the applicable boxes) <!-- Follow the below conventions to check the box -->
+
+<!-- Mark all the applicable boxes. To mark the box as done follow the following conventions -->
+<!--
+[x] - Correct; marked as done
+[ ] - Not correct; marked as **not** done
+-->
+
+- [ ] My code follows the code style of this project.
+- [ ] This PR does not contain plagiarized content.
+- [ ] The title of my pull request is a short description of the requested changes.
+
+## 📄 Note to reviewers
+
+<!-- Add notes to reviewers if applicable -->
+
+## 📷 Screenshots/Link

.github/workflows/AUTO_MESSAGE_ON_ISSUE_OPEN.yml

@@ -0,0 +1,19 @@
+name: Auto message on issue opened
+
+on:
+  issues:
+    types: [opened]
+
+jobs:
+  auto-response:
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: derekprior/add-autoresponse@master
+      env:
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      with:
+        respondableId: ${{ github.event.pull_request.node_id }}
+        response: "Thanks for your first contribution on Aviyelverse @${{ github.event.pull_request.user.login }} :)"
+        author: ${{ github.event.pull_request.user.login }}
+        exemptedAuthors: "Aviyelverse"

.github/workflows/AUTO_MESSAGE_ON_PR_OPEN.yml

@@ -0,0 +1,19 @@
+name: Auto message on pr opened
+
+on:
+  pull_request_target:
+    types: [opened]
+
+jobs:
+  auto-response:
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: derekprior/add-autoresponse@master
+      env:
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      with:
+        respondableId: ${{ github.event.pull_request.node_id }}
+        response: "Thanks for your contribution, @${{ github.event.pull_request.user.login }}! We will review your PR soon :)"
+        author: ${{ github.event.pull_request.user.login }}
+        exemptedAuthors: "Aviyelverse"

.github/workflows/ISSUE_LABELER.yml

@@ -0,0 +1,14 @@
+name: issue-labeler
+
+on:
+  issues:
+    types: [opened]
+
+jobs:
+  automate-issues-labels:
+    runs-on: ubuntu-latest
+    steps:
+      - name: initial labeling
+        uses: andymckay/labeler@master
+        with:
+          add-labels: 'new-issue'

CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# 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, caste, color, 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
+[email protected].
+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.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTING.md

@@ -0,0 +1,90 @@
+# Contribution Guidelines
+
+## Never made an open source contribution before? Wondering how contributions work in our project? Here's a quick rundown!
+
+## Fork this repository
+
+* Fork this repository by clicking on the fork button on the top of this page.
+This will create a copy of this repository in your account.
+
+## Clone the repository
+
+* Now clone the forked repository to your machine. Go to your GitHub account, open the forked repository, click on the code button and then click the _copy to clipboard_ icon.
+
+Open a terminal and run the following git command:
+
+```bash
+git clone "url you just copied"
+```
+
+where "url you just copied" (without the quotation marks) is the url to this repository (your fork of this project). 
+
+```bash
+git clone https://github.com/name/aviyel-first-pr.git
+```
+
+where `name` is your GitHub username. Here you're copying the contents of the Clone-IT repository on GitHub to your computer.
+
+## Navigate to the project directory
+
+* After cloning the project in your computer, navigate to the project file using the command below.
+
+```bash
+cd <cloned-repo>
+```
+
+## Add a reference(remote) to the original repository
+
+```bash
+git remote add upstream https://github.com/aviyelverse/aviyel-first-pr 
+```
+
+* Check the remotes for this repository.
+
+```bash
+git remote -v
+```
+
+* Always take a pull from the upstream repository to your master branch to keep it at par with the main project(updated repository).
+
+```bash
+git pull upstream main
+```
+
+## Create a new branch
+
+```bash
+git checkout -b <your_branch_name>
+```
+
+* Perfom your desired changes to the code base.
+
+* Track your changes:heavy_check_mark: .
+
+```bash
+git add . 
+```
+
+* Commit your changes .
+
+```bash
+git commit -m "Relevant message"
+```
+
+* Push the committed changes in your feature branch to your remote repo.
+
+```bash
+git push -u origin <your_branch_name>
+```
+
+* To create a pull request, click on `compare and pull requests`.
+
+* Add appropriate title and description to your pull request explaining your changes and efforts done.
+
+* Click on `Create Pull Request`.
+
+* Congrats :exclamation: You have made a PR to the Aviyel-First-PR :boom: . Wait for your submission to be accepted and your PR to be merged.
+
+* Wait for the pull request to be reviewed by a maintainer, Make changes to the pull request if the reviewing maintainer recommends them.
+
+* Hooray 🥳  your success after your pull request is merged!