chore(repository): Pretty project

.github/ISSUE_TEMPLATE/bug_report.md

@@ -7,19 +7,17 @@ labels: 'bug'
 
 ## Expected Behavior
 
-
 ## Actual Behavior
 
-
 ## Steps to Reproduce the Problem
 
-  1.
-  2.
-  3.
+1.
+2.
+3.
 
 ## Critical Bug?
 
-- [ ] Yes
-- [ ] No
+-   [ ] Yes
+-   [ ] No
 
-## More Information
+## More Information

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,25 +1,29 @@
 ---
-name: "🚀 Feature request"
+name: '🚀 Feature request'
 title: '[FEAT]: '
 about: If you want to add something new.
 labels: 'feature request'
 assignees: ''
-
 ---
 
 ## Feature Request
 
 **Describe the Feature Request**
+
 <!-- A clear and concise description of what the feature request is. Please include if your feature request is related to a problem. -->
 
 **Describe Preferred Solution**
+
 <!-- A clear and concise description of what you want to happen. -->
 
 **Describe Alternatives**
+
 <!-- A clear and concise description of any alternative solutions or features you've considered. -->
 
 **Related Code**
+
 <!-- If you are able to illustrate the feature request with an example, please provide a sample application via an online code collaborator such as [StackBlitz](https://stackblitz.com), or [GitHub](https://github.com). -->
 
 **Additional Context**
-<!-- List any other information that is relevant to your issue. Stack traces, related issues, suggestions on how to add, use case, Stack Overflow links, forum links, screenshots, OS if applicable, etc. -->
+
+<!-- List any other information that is relevant to your issue. Stack traces, related issues, suggestions on how to add, use case, Stack Overflow links, forum links, screenshots, OS if applicable, etc. -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,30 +1,31 @@
 ## Pull request checklist
 
 Please check if your PR fulfills the following requirements:
-- [ ] Prettier (`npm run prettier`) has passed locally and any fixes were made for failures
-- [ ] Test (`npm run test`) has passed locally
 
+-   [ ] Prettier (`npm run prettier`) has passed locally and any fixes were made for failures
+-   [ ] Test (`npm run test`) has passed locally
 
 ## Pull request type
 
 Please check the type of change your PR introduces:
-- [ ] Bugfix
-- [ ] Feature
-- [ ] Style changes
-- [ ] Code style update (formatting, renaming)
-- [ ] Refactoring (no functional changes, no api changes)
-- [ ] Build related changes
-- [ ] Documentation content changes
-- [ ] Other (please describe): 
 
+-   [ ] Bugfix
+-   [ ] Feature
+-   [ ] Style changes
+-   [ ] Code style update (formatting, renaming)
+-   [ ] Refactoring (no functional changes, no api changes)
+-   [ ] Build related changes
+-   [ ] Documentation content changes
+-   [ ] Other (please describe):
 
 ## What is the current behavior?
+
 <!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
 
 Issue Number: N/A
 
-
 ## What is the new behavior?
+
 <!-- Please describe the behavior or changes that are being added by this PR. -->
 
 -
@@ -33,12 +34,11 @@ Issue Number: N/A
 
 ## Does this introduce a breaking change?
 
-- [ ] Yes
-- [ ] No
+-   [ ] Yes
+-   [ ] No
 
 <!-- If this introduces a breaking change, please describe the impact and migration path for existing applications below. -->
 
-
 ## Other information
 
-<!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. -->
+<!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. -->

.prettierrc.json

@@ -3,4 +3,4 @@
     "tabWidth": 4,
     "semi": false,
     "singleQuote": true
-}
+}

CONTRIBUTING.md

@@ -1,16 +1,19 @@
 # Contributing to Transcriptase
+
 We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
 
-- Reporting a bug
-- Discussing the current state of the code
-- Submitting a fix
-- Proposing new features
-- Becoming a maintainer
+-   Reporting a bug
+-   Discussing the current state of the code
+-   Submitting a fix
+-   Proposing new features
+-   Becoming a maintainer
 
 ## We Develop with Github
+
 We use github to host code, to track issues and feature requests, as well as accept pull requests.
 
 ## We Use [Github Flow](https://guides.github.com/introduction/flow/index.html), So All Code Changes Happen Through Pull Requests
+
 Pull requests are the best way to propose changes to the codebase (we use [Github Flow](https://guides.github.com/introduction/flow/index.html)). We actively welcome your pull requests:
 
 1. Fork the repo and create your branch from `main`.
@@ -21,50 +24,54 @@ Pull requests are the best way to propose changes to the codebase (we use [Githu
 6. Issue that pull request!
 
 ## Any contributions you make will be under the MIT Software License
+
 In short, when you submit code changes, your submissions are understood to be under the same [MIT License](http://choosealicense.com/licenses/mit/) that covers the project. Feel free to contact the maintainers if that's a concern.
 
 ## Report bugs using Github's [issues](https://github.com/BerkeAras/WorkGroup/issues)
+
 We use GitHub issues to track public bugs. Report a bug by [opening a new issue](); it's that easy!
 
 ## Write bug reports with detail, background, and sample code
 
 **Great Bug Reports** tend to have:
 
-- A quick summary and/or background
-- Steps to reproduce
-  - Be specific!
-  - Give sample code if you can. [My stackoverflow question](http://stackoverflow.com/q/12488905/180626) includes sample code that *anyone* with a base R setup can run to reproduce what I was seeing
-- What you expected would happen
-- What actually happens
-- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
+-   A quick summary and/or background
+-   Steps to reproduce
+    -   Be specific!
+    -   Give sample code if you can. [My stackoverflow question](http://stackoverflow.com/q/12488905/180626) includes sample code that _anyone_ with a base R setup can run to reproduce what I was seeing
+-   What you expected would happen
+-   What actually happens
+-   Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
 
 ## Committing Changes
 
 **Great Commits** should be in this format:
 
-``<type>(<scope>): <subject>``
-
- - Types
- 	- **feat**: A new feature
- 	- **fix**: A bug fix
- 	- **docs**: Documentation only changes
- 	- **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- 	- **refactor**: A code change that neither fixes a bug nor adds a feature
- 	- **perf**: A code change that improves performance
- 	- **test**: Adding missing tests
- 	- **chore**: Changes to the build process or auxiliary tools and libraries such as 	documentation generation
-
- - Scopes
-	- For example a specific component (e. g. sidebar, signin-provider, ...)
+`<type>(<scope>): <subject>`
+
+-   Types
+    -   **feat**: A new feature
+    -   **fix**: A bug fix
+    -   **docs**: Documentation only changes
+    -   **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
+    -   **refactor**: A code change that neither fixes a bug nor adds a feature
+    -   **perf**: A code change that improves performance
+    -   **test**: Adding missing tests
+    -   **chore**: Changes to the build process or auxiliary tools and libraries such as documentation generation
+-   Scopes
+    -   For example a specific component (e. g. sidebar, signin-provider, ...)
 
 ## Use a Consistent Coding Style
+
 Use [Airbnb React/JSX Style Guide](https://github.com/airbnb/javascript/tree/master/react)
 
-* 2 spaces for indentation rather than tabs
-* You can try running `npm run lint` for style unification
+-   2 spaces for indentation rather than tabs
+-   You can try running `npm run lint` for style unification
 
 ## License
+
 By contributing, you agree that your contributions will be licensed under its MIT License.
 
 ## References
-This document was adapted from the open-source contribution guidelines for [Facebook's Draft](https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md) and [Ionic Framework](https://github.com/ionic-team/ionic-framework/blob/master/.github/CONTRIBUTING.md)
+
+This document was adapted from the open-source contribution guidelines for [Facebook's Draft](https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md) and [Ionic Framework](https://github.com/ionic-team/ionic-framework/blob/master/.github/CONTRIBUTING.md)

DOT_ENV_TEMPLATE.md

@@ -5,4 +5,4 @@ REACT_APP_AUTHDOMAIN=
 REACT_APP_PROJECTID=
 REACT_APP_STORAGEBUCKET=
 REACT_APP_MESSAGINGSENDERID=
-REACT_APP_APPID=
+REACT_APP_APPID=

README.md

@@ -1 +1 @@
-# WorkGroup
+# WorkGroup