chore: reformat

Signed-off-by: Sefa Eyeoglu <[email protected]>

Author: Scrumplex

.github/CODE_OF_CONDUCT.md

@@ -14,22 +14,22 @@ appearance, race, religion, or sexual identity and orientation.
 Examples of behavior that contributes to creating a positive environment
 include:
 
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
 
 Examples of unacceptable behavior by participants include:
 
-* The use of sexualized language or imagery and unwelcome sexual attention or
- advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
- address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
- professional setting
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
 
 ## Our Responsibilities
 
@@ -70,7 +70,7 @@ members of the project's leadership.
 This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
 available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
 
-[homepage]: https://www.contributor-covenant.org
-
 For answers to common questions about this code of conduct, see
 https://www.contributor-covenant.org/faq
+
+[homepage]: https://www.contributor-covenant.org

.github/CONTRIBUTING.md

@@ -11,32 +11,39 @@ We love your input! We want to make contributing to this project as easy and tra
 If you are proposing new features, please discuss them with us in the [development server](https://discord.gg/etJNHCQ) before you start working on them!
 
 ## We Develop with Github
+
 We use GitHub to host code, to track issues and feature requests, as well as accept pull requests.
 
 ## We Use [Git Flow](https://atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow)
-![Simple Image Of A Git Flow Workflow](https://nvie.com/img/[email protected])  
-When contributing to this project, please make sure you follow this and name your branches appropriately! 
+
+![Simple Image Of A Git Flow Workflow](https://nvie.com/img/[email protected])\
+When contributing to this project, please make sure you follow this and name your branches appropriately!
 
 ## All Code Changes Happen Through Pull Requests
-Make sure you know how Git Flow works before contributing! 
+
+Make sure you know how Git Flow works before contributing!
 Pull requests are the best way to propose changes to the codebase. We actively welcome your pull requests:
 
 1. Fork the repo and create your branch from `master` or `development` according to Git Flow.
-2. Update the CHANGELOG.
-3. If you've changed `core/*` or `bot.py`, mark changelog as "BREAKING" since plugins may break.
-4. Make sure your code passes the lint checks.
-5. Create Issues and pull requests!
+1. Update the CHANGELOG.
+1. If you've changed `core/*` or `bot.py`, mark changelog as "BREAKING" since plugins may break.
+1. Make sure your code passes the lint checks.
+1. Create Issues and pull requests!
 
 ## Any contributions you make will be under the GNU Affero General Public License v3.0
+
 In short, when you submit code changes, your submissions are understood to be under the same [GNU Affero General Public License v3.0](https://www.gnu.org/licenses/agpl-3.0.en.html) that covers the project. Feel free to contact the maintainers if that's a concern.
 
 ## Report bugs using [Github Issues](https://github.com/modmail-dev/modmail/issues)
+
 We use GitHub issues to track public bugs. Report a bug by [opening a new Issue](https://github.com/modmail-dev/modmail/issues/new); it's that easy!
 
 ## Find pre-existing issues to tackle
+
 Check out our [unstaged issue tracker](https://github.com/modmail-dev/modmail/issues?q=is%3Aissue+is%3Aopen+-label%3Astaged) and start helping out!
 
 Ways to help out:
+
 - Help out new members
 - Highlight invalid bugs/unsupported use cases
 - Code review of pull requests
@@ -45,6 +52,7 @@ Ways to help out:
 - Create a pull request to resolve the issue!
 
 ## Write bug reports with detail, background, and sample code
+
 **Great Bug Reports** tend to have:
 
 - A quick summary and background
@@ -55,10 +63,13 @@ Ways to help out:
 - Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
 
 ## Use a Consistent Coding Style
+
 We use [black](https://github.com/python/black) for a unified code style.
 
 ## 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)