diff --git a/.editorconfig b/.editorconfig index 5fe54ca..2bbe8ef 100644 --- a/.editorconfig +++ b/.editorconfig @@ -6,7 +6,7 @@ root = true [*] charset = utf-8 -indent_size = 2 +indent_size = 4 indent_style = space end_of_line = lf insert_final_newline = true diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS new file mode 100644 index 0000000..f7a0035 --- /dev/null +++ b/.github/CODEOWNERS @@ -0,0 +1 @@ +* @N6REJ diff --git a/.github/CODE_OF_CONDUCT.md b/.github/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..80efed1 --- /dev/null +++ b/.github/CODE_OF_CONDUCT.md @@ -0,0 +1,134 @@ + +# 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, caste, color, 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 +[Contact Us](mailto:abuse@bearsampp.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.1, available at +[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1]. + +Community Impact Guidelines were inspired by +[Mozilla's code of conduct enforcement ladder][Mozilla CoC]. + +For answers to common questions about this code of conduct, see the FAQ at +[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at +[https://www.contributor-covenant.org/translations][translations]. + +[homepage]: https://www.contributor-covenant.org +[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html +[Mozilla CoC]: https://github.com/mozilla/diversity +[FAQ]: https://www.contributor-covenant.org/faq +[translations]: https://www.contributor-covenant.org/translations diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md new file mode 100644 index 0000000..0213c06 --- /dev/null +++ b/.github/CONTRIBUTING.md @@ -0,0 +1,5 @@ +# Contributing guidelines + +Please read [the 'Contribute' official page](https://bearsampp.com/contribute). + +You are also bound by our [Contributors Code of Conduct](https://bearsampp.com/code-of-conduct). diff --git a/.github/FUNDING.yml b/.github/FUNDING.yml new file mode 100644 index 0000000..5456cd4 --- /dev/null +++ b/.github/FUNDING.yml @@ -0,0 +1,2 @@ +github: N6REJ +custom: https://www.paypal.me/BearLeeAble diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md new file mode 100644 index 0000000..5169cad --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -0,0 +1,34 @@ +--- +name: Bug report +about: Create a report to help us improve +--- + +### Behaviour + +#### Steps to reproduce this issue + +1. +2. +3. + +#### Expected behaviour + +> Tell me what should happen + +#### Actual behaviour + +> Tell me what happens instead + +### Configuration + +* Bearsampp version and the previous version in case of upgrade: +* Operating system: + +### Logs + +>* Close Bearsampp. +>* Change the `logsVerbose` variable to the value `2` in the `bearsampp.conf` file. +>* Launch Bearsampp and reproduce your issue. +>* Close Bearsampp. +>* Zip the `logs` folder and the `core/tmp` folder. +>* [Drag and drop](https://help.github.com/en/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests) the zip archive here. diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md new file mode 100644 index 0000000..bbcbbe7 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.md @@ -0,0 +1,20 @@ +--- +name: Feature request +about: Suggest an idea for this project +title: '' +labels: '' +assignees: '' + +--- + +**Is your feature request related to a problem? Please describe.** +A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] + +**Describe the solution you'd like** +A clear and concise description of what you want to happen. + +**Describe alternatives you've considered** +A clear and concise description of any alternative solutions or features you've considered. + +**Additional context** +Add any other context or screenshots about the feature request here. diff --git a/.github/ISSUE_TEMPLATE/module_request.md b/.github/ISSUE_TEMPLATE/module_request.md new file mode 100644 index 0000000..a9e3967 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/module_request.md @@ -0,0 +1,13 @@ +--- +name: Module request +about: Do you want a new module to be added? +labels: ":bulb: feature request, :package: module" +--- + +> Please follow this guide to file a proper request report : http://bearsampp.com/request + +* Name: +* Description: +* Website: +* License (e.g. Freeware, OSS, GPL, MIT, etc): +* Comment (anything else which might help): diff --git a/.github/SUPPORT.md b/.github/SUPPORT.md new file mode 100644 index 0000000..3897e67 --- /dev/null +++ b/.github/SUPPORT.md @@ -0,0 +1,20 @@ +

Reporting an issue

+

Before submitting an issue

+Please do a search in open issues to see if the issue or feature request has already been filed and read the FAQ page first.
If you find your issue already exists, make relevant comments and add your reaction.
Use a reaction like  - upvote or  - downvote in place of a “+1” comment.
 If you cannot find an existing issue that describes your bug or feature, submit an issue using the guidelines below. +

+

Writing good bug reports and feature requests

+File a single issue per problem and feature request. + +The more information you can provide, the more likely someone will be successful in reproducing the issue and finding a fix. +You are now ready to create a new issue! +

+

Closure policy

+ diff --git a/.github/auto-comment.yml b/.github/auto-comment.yml new file mode 100644 index 0000000..bd414b5 --- /dev/null +++ b/.github/auto-comment.yml @@ -0,0 +1,10 @@ +# Comment to a new issue. +issueOpened: > + Thank your for raising a issue. We will try and get back to you as soon as possible. + + Please make sure you have given us as much context as possible. + +pullRequestOpened: > + Thank your for raising your pull request. + + Please make sure you have followed our contributing guidelines. We will review it as soon as possible diff --git a/.github/auto-merge.yml b/.github/auto-merge.yml new file mode 100644 index 0000000..6b2a79c --- /dev/null +++ b/.github/auto-merge.yml @@ -0,0 +1,11 @@ +- match: + dependency_type: development + update_type: semver:minor # includes patch updates! + +- match: + dependency_type: production + update_type: security:minor # includes patch updates! + +- match: + dependency_type: production + update_type: semver:patch diff --git a/.github/dependabot.yml b/.github/dependabot.yml new file mode 100644 index 0000000..d0426fd --- /dev/null +++ b/.github/dependabot.yml @@ -0,0 +1,15 @@ +version: 2 +updates: + - package-ecosystem: "github-actions" + directory: "/" + schedule: + interval: "daily" + time: "08:00" + timezone: "America/Chicago" + labels: + - ":robot: bot" + +permissions: + pull-requests: write + issues: write + repository-projects: write diff --git a/.github/labels.yml b/.github/labels.yml new file mode 100644 index 0000000..79670c9 --- /dev/null +++ b/.github/labels.yml @@ -0,0 +1,101 @@ +## more info https://github.com/crazy-max/ghaction-github-labeler +- # bot + name: "bot :robot:" + color: "69cd00" + description: "Used by bots" +- # bug + name: "bug :bug:" + color: "b60205" + description: "For known bugs" + from_name: "bug" +- # Urgent + name: "Urgent :bomb:" + color: "ED7014" + description: "Urgent" +- # dependencies + name: "dependencies :man_cook:" + color: "0366d6" + description: "Dependencies need fixed" +- # documentation + name: "documentation :books:" + color: "c5def5" + description: "" + from_name: "documentation" +- # duplicate + name: "duplicate :busts_in_silhouette:" + color: "cccccc" + description: "Duplicate" +- # enhancement + name: "enhancement :sparkles:" + color: "0054ca" + description: "Improve program" +- # feature request + name: "feature request :bulb:" + color: "0e8a16" + description: "Feature Request" +- # feedback + name: "feedback :mega:" + color: "03a9f4" + description: "" + from: "question" +- # future maybe + name: "future maybe :rocket:" + color: "fef2c0" + description: "Something to consider" +- # good first issue + name: "good first issue :hatching_chick:" + color: "7057ff" + description: "Should be easy" + from: ":hatching_chick: good first issue" +- # help wanted + name: "help wanted :pray:" + color: "4caf50" + description: "Need Help" + from: "help wanted" +- # hold + name: "hold :hand:" + color: "24292f" + description: "Hold for later version" +- # invalid + name: "invalid :no_entry_sign:" + color: "e6e6e6" + description: "Not a bug" +- # needs more info + name: "needs more info :thinking:" + color: "795548" + description: "Need Info" +- # Blocker + name: "Blocker :triangular_flag_on_post:" + color: "ff0000" + description: "Show Stopper" +- # Website + name: "Website :technologist:" + color: "FFFFFF" + description: "Our website" +- # Security + name: "Security :closed_lock_with_key:" + color: "CD5C5C" + description: "Security issue" +- # Has PR + name: "PR :scientist:" + color: "FFFFFF" + description: "Has PR" +- # RTC + name: "RTC :runner:" + color: "87ceeb" + description: "Ready to commit" +- # Sync + name: "Sync :arrow_forward:" + color: "87ceeb" + description: "Sync Action" + from_name: "sync" +- # Won't fix + name: "Wont_fix_it :man_mechanic:" + color: "b45f06" + description: "Won't fix" + from_name: "wontfix" +- # Hacktoberfest + name: "Hacktoberfest-Accepted :mending_heart:" + description: "Accepted for Hacktoberfest" + from_name: "Hacktoberfest accepted" + diff --git a/.github/stale.yml b/.github/stale.yml new file mode 100644 index 0000000..71a8b5b --- /dev/null +++ b/.github/stale.yml @@ -0,0 +1,18 @@ +# Number of days of inactivity before an issue becomes stale +daysUntilStale: 60 +# Number of days of inactivity before a stale issue is closed +daysUntilClose: 14 +# Issues with these labels will never be considered stale +exemptLabels: + - pinned + - security +# Label to use when marking an issue as stale +staleLabel: wontfix +# Comment to post when marking an issue as stale. Set to `false` to disable +markComment: > + This issue has been automatically marked as stale because it has not had + recent activity. It will be closed if no further activity occurs within the next 14days. Thank you + for your contributions. +# Comment to post when closing a stale issue. Set to `false` to disable +closeComment: > + This issue closed by stalebot. diff --git a/.github/workflows/quickpick-dispatcher.yml b/.github/workflows/quickpick-dispatcher.yml new file mode 100644 index 0000000..58c72d5 --- /dev/null +++ b/.github/workflows/quickpick-dispatcher.yml @@ -0,0 +1,24 @@ +name: Quickpick Dispatcher + +on: + pull_request: + types: + - closed + branches: + - 'main' + +jobs: + if_merged: + if: github.event.pull_request.merged == true + runs-on: ubuntu-latest + steps: + - name: Checkout + uses: actions/checkout@v4 + + - name: Invoke workflow in another repo with inputs + uses: benc-uk/workflow-dispatch@v1 + with: + workflow: combine_releases.yml + repo: Bearsampp/Bearsampp + # Required when using the `repo` option. Either a PAT or a token generated from the GitHub app or CLI + token: "${{ secrets.GH_PAT }}" diff --git a/.gitignore b/.gitignore index da1a012..54e84ad 100644 --- a/.gitignore +++ b/.gitignore @@ -1,13 +1,6 @@ # Jetbrains /*.iml /.idea -/.idea/.gitignore -/.idea/deployment.xml -/.idea/discord.xml -/.idea/module-perl.iml -/.idea/modules.xml -/.idea/php.xml -/.idea/vcs.xml # Bearsampp /.dev @@ -16,3 +9,6 @@ .vscode/ .vs/ .vsc/ + +# ignore "current" directories +/**/current