[RSPC] Add .github and .idea files

* GAD-5: Fix responsiveness (#1125)

Co-authored-by: A Anunaya <[email protected]>
Co-authored-by: Aksh Bansal <[email protected]>

* fix requirements and docker-compose

* fix docker compose and dependencies

* add sdk and api folder structure

* add sdk methods and fix some urls

* update models for API

* add urls for api

* add methods for viewing file, inbox, outbox, getting designation with serializers and minor bug fixes

* fix serializers and fix file attachment functionality in forward_file

* sync with upstream

* add views and fix urls

* create file

* create file change

* fix create_file, without upload_file feature

* fix sdk forward_file : accept remarks

* add view_history in sdk

* add blueprint for draft and archive methods to sdk

* fix FileHeaderSerializer to include id

* fix empty file upload error

* fix inbox outbox methods to return unique ids

* fix complete_flag to is_read

* fix inbox outbox methods to not show archived

* add view_archived method to sdk

* add archive_file method to sdk

* fix inbox and outbox output and add support for attachments

* add draft methods to sdk

* fix default values of named params

* fix css for filetracking.html

* fix fts serializer.py

* add dept adding method to sdk

* add helper methods to sdk

* fix inbox based on SDK

* remove track from TabMenu

* fix outbox using SDK

* fix archive view for SDK

* fix Drafts based on SDK

* fix the view file functionality in the web app

* fix frontend

* fix .gitignore to untrack migrations

* database integration error resolved

* 50% usecases implemented

* Added new suggested usecases

* few changes made

* hellooo

* GAD -5 Dashboard Changes (#1325)

* dashboard and usercard updated (#1329)

* Fixing ui bugs (#1335)

* dashboard modified

* dashboard and fts integrated

* Changes made 10/04

* Changes made 10/04/24

* changes after merge

* changes after merge 1

* dashboard edit

* All changes done

* All changes done 2

* PR raise

* error, login handling done

* functions created for better code understanding

* fixed bugs as asked

* all changes done

* edited for better understanding

* edited for better understanding 3

* file tracking usage comments added

* added .github and .idea

---------

Co-authored-by: Harshvardhan Singh <[email protected]>
Co-authored-by: A Anunaya <[email protected]>
Co-authored-by: Aksh Bansal <[email protected]>
Co-authored-by: akshatnema <[email protected]>
Co-authored-by: Aragorn-64 <[email protected]>
Co-authored-by: Divyansh Tripathi <[email protected]>
Co-authored-by: KULADEEP1 <[email protected]>
Co-authored-by: BlackHAWK2001 <[email protected]>
Co-authored-by: Arpit Tak <[email protected]>
Co-authored-by: SukulSarve <[email protected]>

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,27 @@
+---
+name: 🐛 Bug report
+about: Create a report to help us improve
+title: ""
+labels: "bug"
+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/component_refactor.md

@@ -0,0 +1,12 @@
+---
+name: 🔨 Code refactor
+about: Refactor the existing code .
+title: "Refactoring <module_views> views"
+labels: "Level-2, frontend, refactor"
+assignees: ""
+---
+
+Refactoring the `<module_views>` as per the [proposed style](https://docs.google.com/document/d/1GI2Hile8UbGZ82gFe1y4wAVPcNPXip1cmXTzog1S41U/edit).
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,19 @@
+---
+name: 🚀 Feature request
+about: Suggest an idea for this project
+title: ""
+labels: "feature"
+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/ISSUE_TEMPLATE/proposal.md

@@ -0,0 +1,13 @@
+---
+name: 💥 Proposal
+about: Propose a non-trivial change
+title: ""
+labels: "proposal"
+assignees: ""
+---
+
+**Describe your Proposal**
+A clear and concise description of what the proposal is.
+
+**Additional context**
+Add any other context or screenshots about the proposal here.

.github/pull_request_template.md

@@ -0,0 +1,36 @@
+## Issue that this pull request solves
+
+Closes: # (issue number)
+
+## Proposed changes
+
+### Brief description of what is fixed or changed
+
+## Types of changes
+
+_Put an `x` in the boxes that apply_
+
+-   [ ] Bugfix (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)
+-   [ ] Other (please describe):
+
+## Checklist
+
+_Put an `x` in the boxes that apply_
+
+-   [ ] My code follows the [style guidelines of this project](https://docs.google.com/document/d/1GI2Hile8UbGZ82gFe1y4wAVPcNPXip1cmXTzog1S41U/edit)
+-   [ ] I have performed a self-review of my own code
+-   [ ] I have created new branch for this pull request
+-   [ ] I have commented my code, particularly in hard-to-understand areas
+-   [ ] I have made corresponding changes to the documentation
+-   [ ] My changes generate no new warnings
+-   [ ] My changes does not break the current system and it passes all the current test cases.
+
+## Screenshots
+
+Please attach the screenshots of the changes made in case of change in user interface
+
+## Other information
+
+Any other information that is important to this pull request

.github/workflows/welcome-new-contributors.yml

@@ -0,0 +1,18 @@
+name: 'Welcome new contributors'
+
+on:
+  issues:
+    types: [opened]
+  pull_request_target:
+    types: [opened]
+
+jobs:
+  greet-the-contributor:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: garg3133/[email protected]
+      with:
+        token: ${{ secrets.BOT_ACCESS_TOKEN }}
+        is-oauth-token: true
+        issue-message: 'Hi! Thanks for opening your first issue at Fusion. We really appreciate it. :raised_hands:'
+        pr-message: 'Congratulations for making your first Pull Request at Fusion!! :tada: Someone from our team will review it soon.'

.gitignore

@@ -5,7 +5,7 @@ __pycache__/
 
 # IDEs #
 .vscode
-.idea
+# .idea
 
 # Distribution / packaging
 .Python
@@ -73,4 +73,3 @@ node_modules/
 FusionIIIT/static/
 package-lock.json
 
-