From 792bb13a5b296260e5de7e03fba6445a13922851 Mon Sep 17 00:00:00 2001 From: Yasser Tahiri Date: Mon, 25 Oct 2021 02:20:34 +0100 Subject: [PATCH] =?UTF-8?q?chore:=20Delete=20unused=20files=20=E2=9C=A8=20?= =?UTF-8?q?(#5)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .gitattributes | 5 -- .github/Secrets Sync Action.yml | 2 - AUTHOR | 4 - CODE_OF_CONDUCT.md | 128 -------------------------------- CONTRIBUTING.md | 1 - LICENSE | 2 +- MANIFEST.in | 7 -- SECURITY.md | 19 ----- common/views.py | 3 +- requirements.txt | 1 - 10 files changed, 3 insertions(+), 169 deletions(-) delete mode 100644 .gitattributes delete mode 100644 .github/Secrets Sync Action.yml delete mode 100644 AUTHOR delete mode 100644 CODE_OF_CONDUCT.md delete mode 100644 MANIFEST.in delete mode 100644 SECURITY.md diff --git a/.gitattributes b/.gitattributes deleted file mode 100644 index e2a7b23..0000000 --- a/.gitattributes +++ /dev/null @@ -1,5 +0,0 @@ -*html text eol=lf -*css text eol=lf -*js text eol=lf -*python text eol=lf -docs/releases/*.txt merge=union \ No newline at end of file diff --git a/.github/Secrets Sync Action.yml b/.github/Secrets Sync Action.yml deleted file mode 100644 index 8f5ece3..0000000 --- a/.github/Secrets Sync Action.yml +++ /dev/null @@ -1,2 +0,0 @@ -- name: Secrets Sync Action - uses: google/secrets-sync-action@v1.4.1 \ No newline at end of file diff --git a/AUTHOR b/AUTHOR deleted file mode 100644 index 7f2b311..0000000 --- a/AUTHOR +++ /dev/null @@ -1,4 +0,0 @@ -Yasser Tahiri - - Email : yasserth19@protonmail.com - - github : https://github.com/yezz123 - - Website : https://yezz123.me/ \ No newline at end of file diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md deleted file mode 100644 index 1751c1d..0000000 --- a/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,128 +0,0 @@ -# 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 -yasserth19@protonmail.com. -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. diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index d3853c7..0673667 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -14,7 +14,6 @@ These are a few of the ways you can directly contribute to Athena. Using the pa Pull requests are *accepted* for the project. This includes sending code changes via other means than "pull requests". Plainly put, core code you send will not be used. - #### Bug Fixes If you file an Issue for a bug, have located the bug, and found a fix in 10 lines of code or less.... and you wish to share your fix with the community, then feel free to include it with the filed Issue. If it's longer than 10 lines and wish to discuss it, then send an email to yasserth19@protonmail.com. diff --git a/LICENSE b/LICENSE index 8527fa8..3514fb4 100644 --- a/LICENSE +++ b/LICENSE @@ -1,6 +1,6 @@ MIT License -Copyright (c) 2020 Yasser Tahiri +Copyright (c) 2021 Yasser Tahiri Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal diff --git a/MANIFEST.in b/MANIFEST.in deleted file mode 100644 index 1584fbe..0000000 --- a/MANIFEST.in +++ /dev/null @@ -1,7 +0,0 @@ -include AUTHOR -include LICENSE -include MANIFEST.in -include package.json -include requirements.txt -include example_template.pdf - diff --git a/SECURITY.md b/SECURITY.md deleted file mode 100644 index b3cbabc..0000000 --- a/SECURITY.md +++ /dev/null @@ -1,19 +0,0 @@ -# Security Policy - -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. -## Supported Versions - - -| Version | Supported | -| ------- | ------------------ | -| 0.0.0 | :x: | -| 1.0.0 | :white_check_mark: | - -## Reporting a Vulnerability - -Use the [Contributing.md](https://github.com/GDGSNF/My-Business/blob/master/CONTRIBUTING.md) to report a vulnerability. - -- And read the [CODE_OF_CONDUCT.md](https://github.com/GDGSNF/My-Business/blob/master/CODE_OF_CONDUCT.md) diff --git a/common/views.py b/common/views.py index 8c1a486..f9ea1c0 100644 --- a/common/views.py +++ b/common/views.py @@ -26,8 +26,9 @@ def post(self, request): for chunk in new_template.chunks(): destination.write(chunk) messages.add_message( - request, messages.SUCCESS, f"The settings have been sucessfully saved." + request, messages.SUCCESS, "The settings have been sucessfully saved.", ) + form = SettingsForm() return render( request=request, template_name="settings.html", context={"form": form} diff --git a/requirements.txt b/requirements.txt index 124ad1f..52dfb04 100644 --- a/requirements.txt +++ b/requirements.txt @@ -1,4 +1,3 @@ -wheel django django-crispy-forms psycopg2-binary