Merge from develop

.coderabbit.yaml

@@ -0,0 +1,18 @@
+# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
+language: "en-US"
+early_access: false
+reviews:
+  profile: "chill"
+  request_changes_workflow: true
+  high_level_summary: true
+  poem: true
+  review_status: true
+  collapse_walkthrough: false
+  auto_review:
+    enabled: true
+    drafts: false
+    base_branches:
+      - develop
+      - main
+chat:
+  auto_reply: true

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,36 @@
+---
+name: Bug Report
+about: Create a report to help us improve.
+title: Bug Report
+labels: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+
+1.
+2.
+3.
+4.
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Actual behavior**
+A clear and concise description of how the code performed w.r.t expectations.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Additional details**
+Add any other context or screenshots about the feature request here.
+
+**Potential internship candidates**
+
+Please read this if you are planning to apply for a Palisadoes Foundation internship 
+- https://github.com/PalisadoesFoundation/talawa/issues/359

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,28 @@
+---
+name: Feature Request
+about: Suggest an idea for this project
+title: Feature Request
+labels: feature request
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is.
+
+**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.
+
+**Approach to be followed (optional)**
+A clear and concise description of approach to be followed.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.
+
+**Potential internship candidates**
+
+Please read this if you are planning to apply for a Palisadoes Foundation internship 
+- https://github.com/PalisadoesFoundation/talawa/issues/359

.github/dependabot.yaml

@@ -0,0 +1,15 @@
+version: 2
+updates:
+  # Enable version updates for flutter's pub package manager
+  - package-ecosystem: "pub"
+    # Look for `pubspec.yaml` and `pubspec.lock` files in the `root` directory
+    directory: "/"
+    # Check the pub.dev registry for updates every day (weekdays)
+    schedule:
+      interval: "monthly"
+    target-branch: "develop-postgres"
+    # # Add default reviewers
+    # reviewers:
+    #   - "palisadoes"
+    #   - "randomUserName"
+

.github/pull_request_template.md

@@ -1,20 +1,60 @@
-<!-- Thanks for submitting a pull request! Please provide enough information so that others can review your pull request. -->
+<!--
+This section can be deleted after reading.
 
-**What kind of change does this PR introduce?**
+We employ the following branching strategy to simplify the development process and to ensure that only stable code is pushed to the `master` branch:
+
+- `develop`: For unstable code: New features and bug fixes.
+- `master`: Where the stable production-ready code lies. Only security-related bugs.
+
+NOTE!!!
+
+ONLY SUBMIT PRS AGAINST OUR `DEVELOP` BRANCH. THE DEFAULT IS `MAIN`, SO YOU WILL HAVE TO MODIFY THIS BEFORE SUBMITTING YOUR PR FOR REVIEW. PRS MADE AGAINST `MAIN` WILL BE CLOSED.
+-->
+
+<!--
+Thanks for submitting a pull request! Please provide enough information so that others can review your pull request.
+-->
+
+### What kind of change does this PR introduce?
 
 <!-- E.g. a bugfix, feature, refactoring, etc… -->
 
-**Did you add tests for your changes?**
+### Issue Number:
+
+Fixes #<!--Add related issue number here and delete this comment text block.-->
+
+### Did you add tests for your changes?
+
+<!--Yes or No. Note: Add unit tests or automation tests for your code.-->
 
-**If relevant, did you update the documentation?**
+- [ ] Tests are written for all changes made in this PR.
+- [ ] Test coverage meets or exceeds the current coverage (~90/95%).
 
-**Summary**
+Snapshots/Videos:
 
-<!-- Explain the **motivation** for making this change. What existing problem does the pull request solve? -->
+<!--Add snapshots or videos wherever possible.-->
+
+### If relevant, did you update the documentation?
+
+<!--Add link to Talawa-Docs.-->
+
+### Summary
+
+<!-- Explain the motivation for making this change. What existing problem does the pull request solve? -->
 <!-- Try to link to an open issue for more information. -->
 
-**Does this PR introduce a breaking change?**
+### Does this PR introduce a breaking change?
 
 <!-- If this PR introduces a breaking change, please describe the impact and a migration path for existing applications. -->
 
-**Other information**
+### Checklist for Repository Standards
+- [ ] Have you reviewed and implemented all applicable `coderaabbitai` review suggestions?
+- [ ] Have you ensured that the PR aligns with the repository’s contribution guidelines?
+
+### Other information
+
+<!--Add extra information about this PR here-->
+
+### Have you read the [contributing guide](https://github.com/PalisadoesFoundation/talawa/blob/master/CONTRIBUTING.md)?
+
+<!--Yes or No-->

.github/workflows/README.md

@@ -0,0 +1,47 @@
+# Talawa GitHub Workflows Guidelines
+
+Follow these guidelines when contributing to this directory.
+
+## General
+
+Any changes to files in this directory are flagged when pull requests are run. Make changes only on the advice of a contributor.
+
+## YAML Workflow Files
+
+The YAML files in this directory have very specific roles depending on the type of workflow.
+
+Whenever possible you must ensure that:
+1. The file roles below are maintained
+1. The sequence of the jobs in the workflows are maintained using [GitHub Action dependencies](https://docs.github.com/en/actions/learn-github-actions/managing-complex-workflows). 
+
+### File Roles
+Follow these guidelines when creating new YAML defined GitHub actions. This is done to make troubleshooting easier.
+
+1. `Issue` Workflows:
+   1. Place all actions related to issues in the `issues.yml` file.
+1. `Pull Request` workflows to be run by:
+   1. Workflows to run **First Time** repo contributors:
+      1. Place all actions related to to this in the `pull-request-target.yml` file.
+   1. Workflows to be run by **ALL** repo contributors:
+      1. Place all actions related to pull requests in the `pull-request.yml` file.
+1. `Push` workflows:
+   1. Place all actions related to pushes in the `push.yml` file.
+
+#### File Role Exceptions
+
+There are some exceptions to these rules in which jobs can be placed in dedicated separate files:
+1. Jobs that require unique `cron:` schedules 
+1. Jobs that require unique `paths:` statements that operate only when files in a specific path are updated.
+1. Jobs only work correctly if they have a dedicated file (eg. `CodeQL`)
+
+## Scripts
+
+Follow these guidelines when creating or modifying scripts in this directory.
+
+1. All scripts in this directory must be written in python3 for consistency.
+1. The python3 scripts must follow the following coding standards. Run these commands against your scripts before submitting PRs that modify or create python3 scripts in this directory.
+    1. Pycodestyle
+    1. Pydocstyle
+    1. Pylint
+    1. Flake8
+1. All scripts must run a main() function.

.github/workflows/auto-label.json5

@@ -0,0 +1,17 @@
+{
+  labelsSynonyms: {
+    dependencies: ["dependencies", "dependabot", "dependency"],
+    security: ["security"],
+    "good first issue": [
+      "security",
+      "dependencies",
+      "dependabot",
+      "dependency",
+      "layout",
+      "screen",
+      "design",
+      "figma",
+    ],
+    "ui/ux": ["layout", "screen", "design", "figma"],
+  },
+}