.PyGuard v3.1.0.0

.editorconfig

@@ -0,0 +1,12 @@
+# EditorConfig is awesome: https://EditorConfig.org
+
+# top-most EditorConfig file
+root = true
+
+[*]
+indent_style = space
+indent_size = 4
+end_of_line = crlf
+charset = utf-8
+trim_trailing_whitespace = false
+insert_final_newline = false

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @ByteCorum

.github/FUNDING.yml

@@ -0,0 +1,12 @@
+# These are supported funding model platforms
+
+github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
+patreon: # Replace with a single Patreon username
+open_collective: # Replace with a single Open Collective username
+ko_fi: bytecorum # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+otechie: # Replace with a single Otechie username
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,30 @@
+---
+name: Bug Report
+about: Please take your time and provide us some info about an issue that you've faced.
+title: "Bug: <subject>"
+labels: bug, no-priority
+assignees: ByteCorum
+---
+
+### Description
+
+A field to provide the detailed info about faced issue.
+
+### Condition & circumstances
+
+A field to provide the information how did u get this issue and how to reproduce these circumstances.
+
+### Expected behavior
+
+A field to provide the information of what have you expected to happen.
+
+### PC configuration
+
+- CPU:
+- GPU:
+- RAM:
+- OS:
+
+### Additional context
+
+A field to provide any other context about the problem: logs, screenshots, debug info.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Contact Author
+    url: https://discord.com/users/798503509522645012
+    about: Author's discord account.
+  - name: Stackoverflow
+    url: https://stackoverflow.com/users/26622521/bytecorum
+    about: Maybe you can find solution on stackoverflow.

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,25 @@
+---
+name: Feature request
+about: "Please take your time and provide us info about your idea for this project "
+title: "Request: <subject>"
+labels: suggestion, no-priority
+assignees: ByteCorum
+---
+
+### General
+
+- Related issue or pr:
+- Similar to feature in todo:
+- Should be involved in:
+
+### Description
+
+A field to provide the detailed info about your idea and what you want to happen.
+
+### Alternatives
+
+A field to provide the description of any alternative solutions or features you've considered.
+
+### Additional context
+
+A field to provide any other context about the idea: templates, screenshots, code blocks.

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,21 @@
+---
+name: Question
+about: Please take your time and tell us about your question.
+title: "Question: <subject>"
+labels: question, no-priority
+assignees: ByteCorum
+---
+
+### Basic
+
+- Related issue or pr:
+- Related functionality:
+- Should be documented: y/n
+
+### Description
+
+A field to provide the detailed info about faced issue.
+
+### Additional context
+
+A field to provide any other context about the question: screenshots, code blocks.

.github/labels.yml

@@ -0,0 +1,73 @@
+# Type
+- name: "bug"
+  color: ee0701
+  description: "Something isn't working as expected or causes issues."
+- name: "question"
+  color: cc317c
+  description: "Further information is requested or clarification needed."
+- name: "suggestion"
+  color: 84b6eb
+  description: "Ideas for improvements or new features."
+- name: "docs"
+  color: 0075ca
+  description: "Documentation improvements or additions."
+- name: "feat"
+  color: 0e8a16
+  description: "New feature or functionality."
+- name: "fix"
+  color: ee0701
+  description: "Bug fix or correction."
+- name: "style"
+  color: f9d0c4
+  description: "Code style, formatting, or cosmetic changes."
+- name: "refactor"
+  color: fbca04
+  description: "Code restructuring without changing functionality."
+- name: "test"
+  color: 1d76db
+  description: "Adding or updating tests."
+- name: "chore"
+  color: fef2c0
+  description: "Maintenance tasks, build processes, or tooling changes."
+
+# Priority
+- name: "high-priority"
+  color: b60205
+  description: "High priority issue that should be addressed urgently."
+- name: "medium-priority"
+  color: fbca04
+  description: "Medium priority issue for normal workflow."
+- name: "low-priority"
+  color: 0e8a16
+  description: "Low priority issue that can be addressed when time permits."
+- name: "no-priority"
+  color: e4e669
+  description: "No specific priority assigned."
+
+# Status
+- name: "wip-status"
+  color: ff9500
+  description: "Work in progress - currently being worked on."
+- name: "suspended-status"
+  color: 5319e7
+  description: "Work has been suspended or put on hold."
+- name: "invalid-status"
+  color: 000000
+  description: "This issue or pull request is not valid."
+- name: "duplicate-status"
+  color: cccccc
+  description: "This issue or pull request already exists."
+- name: "wontfix-status"
+  color: ffffff
+  description: "This will not be worked on or fixed."
+
+# Impact
+- name: "major"
+  color: d73a4a
+  description: "Major changes with significant impact."
+- name: "minor"
+  color: 0075ca
+  description: "Minor changes with limited impact."
+- name: "regular"
+  color: 28a745
+  description: "Regular changes as part of normal development."

.github/pull_request_template.md

@@ -0,0 +1,31 @@
+<!--- Provide a general summary of your changes in the title above -->
+
+### General
+
+- Related issue:
+- Related functionality:
+- Feature in todo:
+- Should be documented: y/n
+
+<!-- Please try to limit your pull request to one type; submit multiple pull requests if needed. -->
+### Type
+
+- [ ] Bugfix
+- [ ] Feature
+- [ ] Code style update
+- [ ] Refactor
+- [ ] Tests-related changes
+- [ ] Documentation content changes
+- [ ] Other (please describe):
+
+### Description
+
+A field to provide the detailed info about what have you modified.
+
+### Effect
+
+A field to provide the detailed info about how do your changes affect entire project.
+
+## Other information
+
+A field to provide any other context about your changes: logs, screenshots, debug info.

.github/workflows/issues-reply.yml

@@ -0,0 +1,59 @@
+name: Auto-Reply to Issues
+
+on:
+  issues:
+    types: [opened]
+
+jobs:
+  auto-reply:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Reply to issue based on type
+        uses: actions/github-script@v7
+        with:
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+          script: |
+            const issue = context.payload.issue;
+            const issueTitle = issue.title.toLowerCase();
+            const issueBody = issue.body || '';
+            const labels = issue.labels.map(label => label.name);
+            let issueComment = '';
+
+            // Determine issue type and set appropriate response
+            if (labels.includes('bug') || issueTitle.includes('bug:')) {
+              issueComment = `**Thank you for reporting this bug!**
+              We appreciate you taking the time to provide detailed information about the issue you've encountered. Our team will investigate this bug and work on a fix as soon as possible.
+              Thank you for helping us improve our software!`;
+
+            } else if (labels.includes('enhancement') || issueTitle.includes('request:')) {
+              issueComment = `**Thank you for your feature request!**
+              We're excited to hear your ideas for improving our project. Feature requests from our community are valuable and help shape the future direction of our software.
+              Thank you for contributing to our project's growth!`;
+
+            } else if (labels.includes('question') || issueTitle.includes('question:')) {
+              issueComment = `**Thank you for your question!**
+              We're here to help you get the most out of our software. Questions from users help us identify areas where our documentation can be improved.
+              We appreciate your engagement with our project!`;
+
+            } else {
+              // Generic response for unclassified issues
+              issueComment = `**Thank you for opening this issue!**
+              We appreciate you taking the time to contribute to our project. To help us assist you better, please:
+              Our team will review and respond soon. Thank you for using our software!`;
+            }
+
+            // Post the comment
+            await github.rest.issues.createComment({
+              issue_number: context.issue.number,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              body: issueComment
+            });
+
+            // Add reaction to show the bot has processed the issue
+            await github.rest.reactions.createForIssue({
+              issue_number: context.issue.number,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              content: 'eyes'
+            });