Fixes#304: Payment gateway issue fixed

.env.sample

@@ -1,13 +1,13 @@
-//do_not_put_quptes_around_values
+//do_not_put_quotes_around_values
 REACT_APP_BACKEND_URL= https://paws-backend.azurewebsites.net
 
 //vapid
-REACT_APP_VAPID_KEY=  your vapid key
+REACT_APP_VAPID_KEY=  your vapid key 
 
 
 //google maps
 REACT_APP_GOOGLE_MAPS_API_KEY= your google maps api key
 
 //cloudinary(image upload)
 REACT_APP_CLOUDINARY_UPLOAD_URL= your cloudinary url
-REACT_APP_CLOUDINARY_UPLOAD_PRESET= your cloudinary preset
+REACT_APP_CLOUDINARY_UPLOAD_PRESET= your cloudinary preset

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,8 +1,8 @@
 ---
-name: Bug report
-about: Create a report to help us improve
-title: ''
-labels: ''
+name: 🪲 Bug Report
+about: Create a bug report to help us resolving the bug
+title: '🪲[Bug]: '
+labels: 'bug'
 assignees: ''
 
 ---
@@ -35,4 +35,4 @@ If applicable, add screenshots to help explain your problem.
  - Version [e.g. 22]
 
 **Additional context**
-Add any other context about the problem here.
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/docs.md

@@ -0,0 +1,22 @@
+---
+name: 📝 Documentation
+about: Propose changes and improvements to Paws-frontend Docs.
+title: '📝[Docs]: '
+labels: '[enhancement, docs ]'
+assignees: ''
+---
+
+**What Docs changes are you proposing?**
+Provide a clear description of the changes you're proposing for the documentation. Are you suggesting corrections, clarifications, additions, or updates?
+
+**Why do the Docs need this improvement? What is the motivation for this change? How will this change benefit the community?**
+Explain the motivation behind the proposed changes and how they will benefit the community or users of the documentation.
+
+**Describe the solution you'd like**
+Provide a clear and concise description of the changes you'd like to see implemented in the documentation.
+
+**Describe alternatives you've considered**
+If you've thought about alternative approaches or solutions, briefly describe them here.
+
+**Additional context**
+Add any additional context, examples, or screenshots related to the proposed documentation changes.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,8 +1,8 @@
 ---
-name: Feature request
-about: Suggest an idea for this project
-title: ''
-labels: ''
+name: 💡 Feature Request
+about: Suggest an interesting feature idea for this project
+title: '💡[FEATURE]: '
+labels: 'enhancement'
 assignees: ''
 
 ---
@@ -17,4 +17,4 @@ A clear and concise description of what you want to happen.
 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.
+Add any other context or screenshots about the feature request here.

.github/workflows/greetings.yaml

@@ -0,0 +1,16 @@
+name: Greetings
+
+on: [pull_request_target, issues]
+
+jobs:
+  greeting:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      pull-requests: write
+    steps:
+    - uses: actions/first-interaction@v1
+      with:
+        repo-token: ${{ secrets.GITHUB_TOKEN }}
+        issue-message: "Hi there! Thanks for opening this issue. We appreciate your contribution to this open-source project. We aim to respond or assign your issue as soon as possible."
+        pr-message: "Welcome to Our repository.🎊 Thank you so much for taking the time to point this out."

CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# 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
+codewarnab.
+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

@@ -49,3 +49,5 @@
 - to understand how its working please take a look at [Paws System Design](https://excalidraw.com/#json=GMHuRPYEPAvFAn5xM4ok8,8w53-nnoWQeDL0hPE86s9A)
 For setting up backend please refer to [Paws Backend](https://github.com/Innovateninjas/Paws-Backend)
 
+# Gssoc'24 
+ issues under gssoc24 time alloted is 5 days . if a issue needed more time we will mention it while assigning after alloted time is passed if no update is given issue will be assigned to other contributor 

LEARN.md

@@ -0,0 +1,35 @@
+# How to Setup Paws
+
+## **Prerequisites**
+
+1. Any IDE(VSCode recommended)
+2. Node.js **v20.13.1** or later
+3. Basic knowledge of ReactJS(Frontend) and Django(Backend)
+
+## **Front-end Setup**
+
+1. Go to [Innovateninjas/Paws-frontend](https://github.com/Innovateninjas/Paws-frontend).
+2. Fork the repository.
+3.  Install the project using  `npm i`.
+4.  Run the project using  `npm start`.
+5.  Create a new branch using  `git checkout -b <branch_name>`
+6. Check [Contributing.md](https://github.com/Innovateninjas/Paws-frontend/blob/main/CONTRIBUTING.md) for full setup Information.
+
+## **Back-end Setup**
+1. Go to [Innovateninjas/Paws-Backend](https://github.com/Innovateninjas/Paws-Backend)
+2. Fork the repository.
+3. Install the requirements using `pip install -r requirements.txt`
+4. Apply the Migrations using `python manage.py migrate`
+5. Run the project using `python manage.py runserver`
+
+## **Creating Issues(Must Read)**
+Make sure your issues follow the proper guidelines as mentioned here [want to work on a new issue ? Read this ](https://github.com/Innovateninjas/Paws-frontend/issues/342)
+
+For discussions or help join the official discord channel in the GSSOC discord server
+[Click here](https://discordapp.com/channels/1231112132595028008/1240960321904971787)
+
+Rules
+1. Do not create duplicate issues.
+2. Check all issues to make sure you are not creating a duplicate issue.
+3. For UI improvements check [this issue](https://github.com/Innovateninjas/Paws-frontend/issues/242).
+4. For Backend issues create an issue in [Innovateninjas/Paws-Backend](https://github.com/Innovateninjas/Paws-Backend). After you're assigned it will be transferred to [Innovateninjas/Paws-frontend](https://github.com/Innovateninjas/Paws-frontend) and you will be assigned the appropriate points and labels.

README.md

@@ -65,12 +65,13 @@ Planned features:
 
 
 ## Are you an NGO?
-Please Contact us at : [email]([email protected])
+Please Contact us at : [email](mailto:[email protected])
 
 
 
 ## Contributing 👨‍💻 
 ### Check Out   [CONTRIBUTING.md](/CONTRIBUTING.md)
+### If your are a beginner check [LEARN.md](/LEARN.md)
 
 
 
@@ -111,6 +112,12 @@ Paws is licensed under the GPL License - see the [LICENSE](LICENSE) file for det
   </a>
 </p>
 
+<div align=center>
+  <h2>This Project is the part of</h2>
+  <img alt="GSSoC" src="https://raw.githubusercontent.com/GirlScriptSummerOfCode/MentorshipProgram/master/GSsoc%20Type%20Logo%20Black.png#gh-light-mode-only" width=87%>
+  <img alt="GSSoC" src="https://user-images.githubusercontent.com/63473496/213306279-338f7ce9-9a9f-4427-8c2a-3e344874498f.png#gh-dark-mode-only"/>
+</div>
+
 ### If you like our work, please star the repository.