Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Main #6

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from
Open

Main #6

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d681a46
frontend build
NxPKG Nov 9, 2024
a31a299
pyzn/frontend add (#5)
NxPKG Nov 9, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
0 frontend/.eslintrc.json → .eslintrc.json
View file
Open in desktop
File renamed without changes.
8 changes: 8 additions & 0 deletions .github/CODEOWNERS
View file
Open in desktop
Validating CODEOWNERS rules …
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
# Code Owners helps give greater control to those who developed a feature
# PR's which modify files that you own will be marked as trusted
# After developing a feature, you can add yourself as it's owner
# Each line starts with file pattern, followed by one or more owners
# Codeowners Docs: https://github.blog/2017-07-06-introducing-code-owners/

# Repo Owners
* @khulnasoft @gitworkflows @gitworkflows @khulnasoft-bot
128 changes: 128 additions & 0 deletions .github/CODE_OF_CONDUCT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,128 @@
# 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
[email protected]
All complaints will be reviewed and investigated promptly and fairly.
Comment on lines +61 to +64
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codebase verification

Email address inconsistency detected

The repository shows that [email protected] is used as the support contact email in the application code, while the Code of Conduct uses [email protected]. This inconsistency needs to be addressed:

Consider standardizing the contact email address across the codebase or using a dedicated email address for Code of Conduct related issues.

🔗 Analysis chain

Verify the contact email address.

Please confirm that [email protected] is the correct email address for Code of Conduct violations. Consider whether a dedicated email address for conduct-related issues would be more appropriate.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if this email is used consistently across the repository
rg -i "[email protected]"

# Check for any other potential contact emails in markdown files
fd -e md -x rg -i "mailto:|@.*\.com"

Length of output: 69

Script:

#!/bin/bash
# Let's try a broader search for email patterns in the code of conduct file
cat .github/CODE_OF_CONDUCT.md

# Also search for any other code of conduct files that might exist
fd "code.*conduct" -I

# Search for any email addresses in the repository
rg -i "[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}"

Length of output: 6170

🧰 Tools
🪛 Markdownlint

63-63: null
Bare URL used

(MD034, no-bare-urls)


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.
80 changes: 80 additions & 0 deletions .github/ISSUE_TEMPLATE/bug.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,80 @@
name: Bug Report 🐛
description: Report something that's not working the way it's (probably) intended to
title: '[BUG] <title>'
labels: ['🐛 Bug']
assignees:
- KhulnaSoft-bot
- NxPkg
body:
- type: dropdown
id: environment
attributes:
label: Environment
description: Where are you running PyZn?
options:
- Self-Hosted (Docker)
- Self-Hosted (Bare Metal)
- Cloud Service (Static)
- Other (Specify below)
validations:
required: true
- type: input
id: system
attributes:
label: System
description: >-
For deployment issues, specify your [distro or OS](https://whatsmyos.com/) and/ or Docker version.
For client-side issues, include your [browser version](https://www.whatsmybrowser.org/)
placeholder: e.g. Firefox 101, Manjaro Linux 21.3.0, Docker 20.10.16
validations:
required: false
Comment on lines +25 to +30
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Make system info required and provide alternatives.

System information is crucial for debugging but:

  1. External services (whatsmyos.com, whatsmybrowser.org) might be unavailable
  2. This field should be required for effective troubleshooting

Consider this revision:

     description: >-
-      For deployment issues, specify your [distro or OS](https://whatsmyos.com/) and/ or Docker version.
-      For client-side issues, include your [browser version](https://www.whatsmybrowser.org/)
+      For deployment issues, specify your OS (run `uname -a` on Linux/Mac or check System Settings on Windows) and Docker version (`docker --version`).
+      For client-side issues, check your browser's About page for version info.
     validations:
-      required: false
+      required: true
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
description: >-
For deployment issues, specify your [distro or OS](https://whatsmyos.com/) and/ or Docker version.
For client-side issues, include your [browser version](https://www.whatsmybrowser.org/)
placeholder: e.g. Firefox 101, Manjaro Linux 21.3.0, Docker 20.10.16
validations:
required: false
description: >-
For deployment issues, specify your OS (run `uname -a` on Linux/Mac or check System Settings on Windows) and Docker version (`docker --version`).
For client-side issues, check your browser's About page for version info.
placeholder: e.g. Firefox 101, Manjaro Linux 21.3.0, Docker 20.10.16
validations:
required: true

- type: input
id: version
attributes:
label: Version
description: What version of PyZn are you running?
placeholder: 4.2.0 ← should look like this (check config menu)
validations:
required: false
Comment on lines +31 to +38
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Make version information required.

Version information is crucial for bug reports and should be mandatory. This helps prevent incomplete reports and speeds up the debugging process.

     validations:
-      required: false
+      required: true
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- type: input
id: version
attributes:
label: Version
description: What version of PyZn are you running?
placeholder: 4.2.0 ← should look like this (check config menu)
validations:
required: false
- type: input
id: version
attributes:
label: Version
description: What version of PyZn are you running?
placeholder: 4.2.0 ← should look like this (check config menu)
validations:
required: true

Comment on lines +31 to +38
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Make version required with format validation.

Version information is crucial for bug tracking and should be:

  1. Required
  2. Validated against semantic versioning format
     validations:
-      required: false
+      required: true
+      pattern: ^\d+\.\d+\.\d+$
+      pattern_error: Please provide version in X.Y.Z format (e.g., 4.2.0)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- type: input
id: version
attributes:
label: Version
description: What version of PyZn are you running?
placeholder: 4.2.0 ← should look like this (check config menu)
validations:
required: false
- type: input
id: version
attributes:
label: Version
description: What version of PyZn are you running?
placeholder: 4.2.0 ← should look like this (check config menu)
validations:
required: true
pattern: ^\d+\.\d+\.\d+$
pattern_error: Please provide version in X.Y.Z format (e.g., 4.2.0)

- type: textarea
id: repro
attributes:
label: Describe the problem
description: Please describe exactly what is not working, include the steps to reproduce, actual result and expected result
placeholder: When doing ABC then DEF, I expect to see XYZ, but I actually see ZYX
validations:
required: true
- type: textarea
id: logs
attributes:
label: Additional info
description: Logs? Screenshots? Yes, please.
placeholder: If the issue happens during build-time, include terminal logs. For run-time errors, include browser logs which you can view in the Dev Tools (F12), under the Console tab. Take care to blank out any personal info.
validations:
required: false
- type: checkboxes
id: idiot-check
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Use a more professional ID for the verification checklist.

The current ID "idiot-check" could be considered unprofessional or offensive.

-    id: idiot-check
+    id: verification-checklist
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
id: idiot-check
id: verification-checklist

attributes:
label: Please tick the boxes
description: Before submitting, please ensure that
options:
- label: You have explained the issue clearly, and included all relevant info
required: true
- label: You are using a [supported](https://github.com/khulnaSoft/pyzn/blob/master/.github/SECURITY.md#supported-versions) version of PyZn
required: true
- label: You've checked that this [issue hasn't already been raised](https://github.com/khulnaSoft/pyzn/issues?q=is%3Aissue)
required: true
- label: You've checked the [docs](https://github.com/khulnaSoft/pyzn/tree/master/docs#readme) and [troubleshooting](https://github.com/khulnaSoft/pyzn/blob/master/docs/troubleshooting.md#troubleshooting) guide ![important](https://img.shields.io/badge/Important!-F6094E)
required: true
- label: You agree to the [code of conduct](https://github.com/khulnaSoft/pyzn/blob/master/.github/CODE_OF_CONDUCT.md#contributor-covenant-code-of-conduct)
required: true
Comment on lines +55 to +70
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Improve ID naming and link accessibility.

  1. The ID "idiot-check" is unprofessional and should be renamed.
  2. The links in the checklist should include aria-labels for better accessibility.
-    id: idiot-check
+    id: verification-checklist
     attributes:
       label: Please tick the boxes
       description: Before submitting, please ensure that
       options:
         - label: You have explained the issue clearly, and included all relevant info
           required: true
-        - label: You are using a [supported](https://github.com/khulnaSoft/pyzn/blob/master/.github/SECURITY.md#supported-versions) version of PyZn
+        - label: You are using a [supported](https://github.com/khulnaSoft/pyzn/blob/master/.github/SECURITY.md#supported-versions "View supported versions") version of PyZn

Committable suggestion skipped: line range outside the PR's diff.

- type: markdown
attributes:
value: |-
## Thanks 🙏
<img align="left" width="160" src="https://i.ibb.co/S5vCnhL/gh-thanks.gif" alt="🐙" />
Thank you for raising this ticket - in doing so you are helping to make the app better for everyone 💪<br>
You should expect a reply within the next 48 hours :)<br>
⭐️ Consider dropping the repo a star if you're enjoying PyZn!<br>
Comment on lines +73 to +78
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Revise the thank you message for sustainability.

Current implementation has potential issues:

  1. The image URL (i.ibb.co) might become unavailable
  2. The 48-hour response promise might set unrealistic expectations

Consider:

  1. Moving the image to the repository's assets
  2. Using more flexible language about response times
      value: |-
        ## Thanks 🙏
-        <img align="left" width="160" src="https://i.ibb.co/S5vCnhL/gh-thanks.gif" alt="🐙" />
+        <img align="left" width="160" src="../assets/thanks.gif" alt="🐙" />
        Thank you for raising this ticket - in doing so you are helping to make the app better for everyone 💪<br>
-        You should expect a reply within the next 48 hours :)<br>
+        We'll review your report as soon as possible :)<br>
        ⭐️ Consider dropping the repo a star if you're enjoying PyZn!<br>

Committable suggestion skipped: line range outside the PR's diff.

validations:
required: false
64 changes: 64 additions & 0 deletions .github/ISSUE_TEMPLATE/feature-request.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,64 @@
name: Feature Request ✨
description: Suggest an idea for future development of PyZn
title: '[FEATURE_REQUEST] <title>'
labels: ['🦄 Feature Request']
assignees:
- KhulnaSoft-bot

Comment on lines +1 to +7
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codebase verification

Bot assignee needs to be updated to match repository configuration

The template currently assigns issues to KhulnaSoft-bot, but the repository collaborator list shows khulnasoft-bot (lowercase). This inconsistency should be fixed by updating the assignee in the feature request template to match the actual bot account name.

  • Update line 6 in .github/ISSUE_TEMPLATE/feature-request.yml to use khulnasoft-bot instead of KhulnaSoft-bot
🔗 Analysis chain

Verify the bot assignee configuration.

The template automatically assigns issues to KhulnaSoft-bot. Please ensure this bot account exists and has the necessary permissions to be assigned to issues.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify if the bot account exists and has necessary permissions
# Expected: The account should exist and have proper access

# Check if the bot account exists in the repository collaborators
gh api repos/khulnasoft/pyzn/collaborators/KhulnaSoft-bot --silent || echo "Bot account not found or lacks access"

Length of output: 68

Script:

#!/bin/bash
# Let's try a different approach to verify the bot configuration

# Check all repository collaborators to see if the bot is listed
gh api repos/khulnasoft/pyzn/collaborators --jq '.[].login'

# Also check recent issues to see if this bot has been active
gh api repos/khulnasoft/pyzn/issues --jq '.[] | select(.assignee != null) | {assignee: .assignee.login}' | head -n 5

# Check other issue templates to see if this bot is referenced elsewhere
fd -e yml -e yaml . .github/ISSUE_TEMPLATE/ -x cat {}

Length of output: 9765

body:

# Field 1 - Is it bug-related
- type: textarea
id: issue
attributes:
label: Is your feature request related to a problem? If so, please describe.
description:
placeholder: A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
validations:
required: false

# Field 2 - Describe feature
- type: textarea
id: solution
attributes:
label: Describe the solution you'd like
placeholder: An outline of how you would like this to be implemented, include as much details as possible
validations:
required: true

# Field 3 - Priority
- type: dropdown
id: priority
attributes:
label: Priority
description: How urgent is the development of this feature
options:
- Low (Nice-to-have)
- Medium (Would be very useful)
- High (The app does not function without it)
validations:
required: true

# Field 3 - Can the user implement
- type: dropdown
id: canImplement
attributes:
label: Is this something you would be keen to implement
description: Are you raising this ticket in order to get an issue number for your PR?
options:
- 'No'
- 'Maybe'
- 'Yes!'
validations:
required: false

# Final text
- type: markdown
attributes:
value: |-
## Thanks 🙏
Thank you for your feature suggestion, you should expect a reply within 48 hours :)
Please note that there is no guarantee that your idea will be implemented
If you haven't already done so, please Star the PyZn's repository on GitHub, to help other users discover it
validations:
required: false
66 changes: 66 additions & 0 deletions .github/ISSUE_TEMPLATE/question.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,66 @@
name: Question 🤷‍♂️
description: Got a question about PyZn, deployment, development or usage?
title: '[QUESTION] <title>'
labels: ['🤷‍♂️ Question']
assignees:
- khulnasoft-bot
Comment on lines +5 to +6
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codebase verification

Bot account exists but lacks repository access

The khulnasoft-bot account exists but appears to lack the necessary repository access and organization membership to be assigned to issues. This could prevent the bot from functioning as intended in the issue template.

  • The bot account exists but is not a public member of the organization
  • The bot is not a repository collaborator
  • Without proper access, the bot won't be able to be assigned to issues
🔗 Analysis chain

Verify bot account and permissions.

Ensure that the khulnasoft-bot account exists and has appropriate permissions to be assigned to issues.

I'll verify the bot's repository and organization access to ensure it can be assigned to issues. The previous output confirmed the bot account exists, but we need to check its permissions.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the bot account exists and has appropriate permissions
# Expected: The bot account should be a member of the organization

# Test: Check if the bot account exists and its role
gh api -H "Accept: application/vnd.github+json" /users/khulnasoft-bot

Length of output: 1502

Script:

#!/bin/bash
# Check if the bot has appropriate permissions in the repository
gh api -H "Accept: application/vnd.github+json" /repos/khulnasoft/khulnasoft-code/collaborators/khulnasoft-bot

# Also check organization membership
gh api -H "Accept: application/vnd.github+json" /orgs/khulnasoft/members/khulnasoft-bot

Length of output: 676


body:
# Filed 1 - Intro Text
- type: markdown
attributes:
value: >
Thanks for using PyZn! Questions are welcome, but in the future will be moving over to
[Discussions](https://github.com/khulnaSoft/pyzn/discussions) page.
Quick questions should be asked [here](https://github.com/khulnaSoft/pyzn/discussions/148) instead.
Comment on lines +13 to +15
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Avoid hardcoding specific discussion thread numbers.

The quick questions link points to a specific discussion thread (#148) which might get archived or locked in the future. Consider:

  1. Using a category link instead of a specific thread
  2. Creating a pinned discussion for questions and linking to that
-        Quick questions should be asked [here](https://github.com/khulnaSoft/pyzn/discussions/148) instead.
+        Quick questions should be asked in our [Q&A Discussion Category](https://github.com/khulnaSoft/pyzn/discussions/categories/q-a) instead.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Thanks for using PyZn! Questions are welcome, but in the future will be moving over to
[Discussions](https://github.com/khulnaSoft/pyzn/discussions) page.
Quick questions should be asked [here](https://github.com/khulnaSoft/pyzn/discussions/148) instead.
Thanks for using PyZn! Questions are welcome, but in the future will be moving over to
[Discussions](https://github.com/khulnaSoft/pyzn/discussions) page.
Quick questions should be asked in our [Q&A Discussion Category](https://github.com/khulnaSoft/pyzn/discussions/categories/q-a) instead.

validations:
required: false

# Field 2 - The actual question
- type: textarea
id: question
attributes:
label: Question
description: Outline your question in a clear and concise manner
validations:
required: true

# Field 3 - Category
- type: dropdown
id: category
attributes:
label: Category
description: What part of the application does this relate to?
options:
- Setup and Deployment
- Configuration
- App Usage
- Development
- Documentation
- Alternate Views
- Authentication
- Using Icons
- Widgets
- Actions
- Language Support
- Search & Shortcuts
- Status Checking
- Theming & Layout
validations:
required: true

# Field 4 - User has RTFM first, and agrees to code of conduct, etc
- type: checkboxes
id: idiot-check
Comment on lines +53 to +54
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Replace inappropriate ID name with a professional alternative.

The current ID name "idiot-check" could be considered offensive or unprofessional.

-    id: idiot-check
+    id: pre-submission-checklist
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- type: checkboxes
id: idiot-check
- type: checkboxes
id: pre-submission-checklist

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Replace unprofessional ID name.

The ID "idiot-check" could be considered offensive or unprofessional. Consider using a more appropriate name like "pre-submission-checklist" or "submission-requirements".

-    id: idiot-check
+    id: pre-submission-checklist
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
id: idiot-check
id: pre-submission-checklist

attributes:
label: Please tick the boxes
description: Before submitting, please ensure that
options:
- label: You are using a [supported](https://github.com/khulnaSoft/pyzn/blob/master/.github/SECURITY.md#supported-versions) version of PyZn (check the first two digits of the version number)
required: true
- label: You've checked that this [question hasn't already been raised](https://github.com/khulnaSoft/pyzn/issues?q=is%3Aissue)
required: true
- label: You've checked the [docs](https://github.com/khulnaSoft/pyzn/tree/master/docs#readme) and [troubleshooting](https://github.com/khulnaSoft/pyzn/blob/master/docs/troubleshooting.md#troubleshooting) guide
required: true
- label: You agree to the [code of conduct](https://github.com/khulnaSoft/pyzn/blob/master/.github/CODE_OF_CONDUCT.md#contributor-covenant-code-of-conduct)
required: true
9 changes: 9 additions & 0 deletions .github/ISSUE_TEMPLATE/share-feedback.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
---
name: "Share Feedback \U0001F308"
about: Share what you think about PyZn, and any ideas or suggestions you have
title: "[FEEDBACK]"
labels: "\U0001F308 Feedback"
assignees: ''

---

Loading
Loading