Skip to content

Commit c207f88

Browse files
N6REJN6REJ
authored
Merge branch 'main' into reset
2 parents 0fbcc4a + a4e7b50 commit c207f88

40 files changed

+661
-296
lines changed

‎.gitattributes‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
# All files are checked into the repo with LF
2+
* text=auto
3+
4+
# These files are checked out using CRLF locally
5+
*.bat eol=crlf
6+
*.dll eol=crlf

‎.github/CODE_OF_CONDUCT.md‎

Lines changed: 134 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,134 @@
1+
2+
# Contributor Covenant Code of Conduct
3+
4+
## Our Pledge
5+
6+
We as members, contributors, and leaders pledge to make participation in our
7+
community a harassment-free experience for everyone, regardless of age, body
8+
size, visible or invisible disability, ethnicity, sex characteristics, gender
9+
identity and expression, level of experience, education, socio-economic status,
10+
nationality, personal appearance, race, caste, color, religion, or sexual
11+
identity and orientation.
12+
13+
We pledge to act and interact in ways that contribute to an open, welcoming,
14+
diverse, inclusive, and healthy community.
15+
16+
## Our Standards
17+
18+
Examples of behavior that contributes to a positive environment for our
19+
community include:
20+
21+
* Demonstrating empathy and kindness toward other people
22+
* Being respectful of differing opinions, viewpoints, and experiences
23+
* Giving and gracefully accepting constructive feedback
24+
* Accepting responsibility and apologizing to those affected by our mistakes,
25+
and learning from the experience
26+
* Focusing on what is best not just for us as individuals, but for the overall
27+
community
28+
29+
Examples of unacceptable behavior include:
30+
31+
* The use of sexualized language or imagery, and sexual attention or advances of
32+
any kind
33+
* Trolling, insulting or derogatory comments, and personal or political attacks
34+
* Public or private harassment
35+
* Publishing others' private information, such as a physical or email address,
36+
without their explicit permission
37+
* Other conduct which could reasonably be considered inappropriate in a
38+
professional setting
39+
40+
## Enforcement Responsibilities
41+
42+
Community leaders are responsible for clarifying and enforcing our standards of
43+
acceptable behavior and will take appropriate and fair corrective action in
44+
response to any behavior that they deem inappropriate, threatening, offensive,
45+
or harmful.
46+
47+
Community leaders have the right and responsibility to remove, edit, or reject
48+
comments, commits, code, wiki edits, issues, and other contributions that are
49+
not aligned to this Code of Conduct, and will communicate reasons for moderation
50+
decisions when appropriate.
51+
52+
## Scope
53+
54+
This Code of Conduct applies within all community spaces, and also applies when
55+
an individual is officially representing the community in public spaces.
56+
Examples of representing our community include using an official e-mail address,
57+
posting via an official social media account, or acting as an appointed
58+
representative at an online or offline event.
59+
60+
## Enforcement
61+
62+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
63+
reported to the community leaders responsible for enforcement at
64+
[Contact Us](mailto:[email protected])
65+
66+
All complaints will be reviewed and investigated promptly and fairly.
67+
68+
All community leaders are obligated to respect the privacy and security of the
69+
reporter of any incident.
70+
71+
## Enforcement Guidelines
72+
73+
Community leaders will follow these Community Impact Guidelines in determining
74+
the consequences for any action they deem in violation of this Code of Conduct:
75+
76+
### 1. Correction
77+
78+
**Community Impact**: Use of inappropriate language or other behavior deemed
79+
unprofessional or unwelcome in the community.
80+
81+
**Consequence**: A private, written warning from community leaders, providing
82+
clarity around the nature of the violation and an explanation of why the
83+
behavior was inappropriate. A public apology may be requested.
84+
85+
### 2. Warning
86+
87+
**Community Impact**: A violation through a single incident or series of
88+
actions.
89+
90+
**Consequence**: A warning with consequences for continued behavior. No
91+
interaction with the people involved, including unsolicited interaction with
92+
those enforcing the Code of Conduct, for a specified period of time. This
93+
includes avoiding interactions in community spaces as well as external channels
94+
like social media. Violating these terms may lead to a temporary or permanent
95+
ban.
96+
97+
### 3. Temporary Ban
98+
99+
**Community Impact**: A serious violation of community standards, including
100+
sustained inappropriate behavior.
101+
102+
**Consequence**: A temporary ban from any sort of interaction or public
103+
communication with the community for a specified period of time. No public or
104+
private interaction with the people involved, including unsolicited interaction
105+
with those enforcing the Code of Conduct, is allowed during this period.
106+
Violating these terms may lead to a permanent ban.
107+
108+
### 4. Permanent Ban
109+
110+
**Community Impact**: Demonstrating a pattern of violation of community
111+
standards, including sustained inappropriate behavior, harassment of an
112+
individual, or aggression toward or disparagement of classes of individuals.
113+
114+
**Consequence**: A permanent ban from any sort of public interaction within the
115+
community.
116+
117+
## Attribution
118+
119+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
120+
version 2.1, available at
121+
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
122+
123+
Community Impact Guidelines were inspired by
124+
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
125+
126+
For answers to common questions about this code of conduct, see the FAQ at
127+
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
128+
[https://www.contributor-covenant.org/translations][translations].
129+
130+
[homepage]: https://www.contributor-covenant.org
131+
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
132+
[Mozilla CoC]: https://github.com/mozilla/diversity
133+
[FAQ]: https://www.contributor-covenant.org/faq
134+
[translations]: https://www.contributor-covenant.org/translations

‎.github/CONTRIBUTING.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,5 @@
11
# Contributing guidelines
22

33
Please read [the 'Contribute' official page](https://bearsampp.com/contribute).
4+
5+
You are also bound by our [Contributors Code of Conduct](https://bearsampp.com/code-of-conduct).

‎.github/ISSUE_TEMPLATE/bug_report.md‎

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
---
5+
6+
### Behaviour
7+
8+
#### Steps to reproduce this issue
9+
10+
1.
11+
2.
12+
3.
13+
14+
#### Expected behaviour
15+
16+
> Tell me what should happen
17+
18+
#### Actual behaviour
19+
20+
> Tell me what happens instead
21+
22+
### Configuration
23+
24+
* Bearsampp version and the previous version in case of upgrade:
25+
* Operating system:
26+
27+
### Logs
28+
29+
>* Close Bearsampp.
30+
>* Change the `logsVerbose` variable to the value `2` in the `bearsampp.conf` file.
31+
>* Launch Bearsampp and reproduce your issue.
32+
>* Close Bearsampp.
33+
>* Zip the `logs` folder and the `core/tmp` folder.
34+
>* [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.

‎.github/ISSUE_TEMPLATE/feature_request.md‎

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**Is your feature request related to a problem? Please describe.**
11+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12+
13+
**Describe the solution you'd like**
14+
A clear and concise description of what you want to happen.
15+
16+
**Describe alternatives you've considered**
17+
A clear and concise description of any alternative solutions or features you've considered.
18+
19+
**Additional context**
20+
Add any other context or screenshots about the feature request here.

‎.github/ISSUE_TEMPLATE/module_request.md‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
name: Module request
3+
about: Do you want a new module to be added?
4+
labels: ":bulb: feature request, :package: module"
5+
---
6+
7+
> Please follow this guide to file a proper request report : http://bearsampp.com/request
8+
9+
* Name:
10+
* Description:
11+
* Website:
12+
* License (e.g. Freeware, OSS, GPL, MIT, etc):
13+
* Comment (anything else which might help):

‎.github/SUPPORT.md‎

Lines changed: 20 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -1,29 +1,20 @@
1-
# Support [![](https://isitmaintained.com/badge/resolution/bearsampp/bearsampp.svg)](https://isitmaintained.com/project/bearsampp/bearsampp)
2-
3-
## Reporting an issue
4-
5-
Please do a search in [open issues](https://github.com/bearsampp/bearsampp/issues?utf8=%E2%9C%93&q=) to see if the issue or feature request has already been filed and read the [FAQ](https://bearsampp.github.io/doc/faq/) page first.
6-
7-
If you find your issue already exists, make relevant comments and add your [reaction](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments). Use a reaction in place of a "+1" comment.
8-
9-
:+1: - upvote
10-
11-
:-1: - downvote
12-
13-
If you cannot find an existing issue that describes your bug or feature, submit an issue using the guidelines below.
14-
15-
## Writing good bug reports and feature requests
16-
17-
File a single issue per problem and feature request.
18-
19-
* Do not enumerate multiple bugs or feature requests in the same issue.
20-
* Do not add your issue as a comment to an existing issue unless it's for the identical input. Many issues look similar, but have different causes.
21-
22-
The more information you can provide, the more likely someone will be successful reproducing the issue and finding a fix.
23-
24-
You are now ready to [create a new issue](https://github.com/bearsampp/bearsampp/issues/new/choose)!
25-
26-
## Closure policy
27-
28-
* Issues that don't have the information requested above (when applicable) will be closed immediately and the poster directed to the support guidelines.
29-
* Issues that go a week without a response from original poster are subject to closure at my discretion.
1+
<h1 class="intro-header text-center">Reporting an issue</h1>
2+
<h3 id="before-submitting-an-issue">Before submitting an issue</h3>
3+
<span>Please do a search in <a href="https://github.com/bearsampp/bearsampp/issues" target="_blank" class="docs-creator" rel="noopener">open issues</a> to see if the issue or feature request has already been filed and read the <a href="https://bearsampp.com/faq/" class="docs-creator">FAQ</a> page first.<br /></span><span>If you find your issue already exists, make relevant comments and add your <a href="https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments" target="_blank" class="docs-creator" rel="noopener">reaction</a>.<br />Use a reaction like </span> <span><img title="+1" alt="" src="https://github.githubassets.com/images/icons/emoji/unicode/1f44d.png" height="16" width="16" /> - upvote or </span> <span><img title="-1" alt="" src="https://github.githubassets.com/images/icons/emoji/unicode/1f44e.png" height="16" width="16" /> - downvote in place of a “+1” comment.<br /></span> <span>If you cannot find an existing issue that describes your bug or feature, submit an issue using the guidelines below.</span>
4+
<p></p>
5+
<h3 id="writing-good-bug-reports-and-feature-requests">Writing good bug reports and feature requests</h3>
6+
<span>File a single issue per problem and feature request.</span>
7+
<ul>
8+
<li>Do not enumerate multiple bugs or feature requests in the same issue.</li>
9+
<li>Do not add your issue as a comment to an existing issue unless it’s for the identical input. Many issues look similar, but have different causes.</li>
10+
<li>Do include images and/or video if it helps explain your issue better.</li>
11+
<li>Do not use any language other then english</li>
12+
</ul>
13+
<span>The more information you can provide, the more likely someone will be successful in reproducing the issue and finding a fix.</span>
14+
<span>You are now ready to <a href="https://github.com/bearsampp/bearsampp/issues/new/choose" target="_blank" class="docs-creator" rel="noopener">create a new issue</a>!</span>
15+
<p></p>
16+
<h3 id="closure-policy">Closure policy</h3>
17+
<ul>
18+
<li>Issues that don’t have the information requested above (when applicable) will be closed immediately and the poster directed to the support guidelines.</li>
19+
<li>Issues that go a week without a response from original poster are subject to closure at our discretion.</li>
20+
</ul>

‎.github/auto-merge.yml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
- match:
2+
dependency_type: development
3+
update_type: semver:minor # includes patch updates!
4+
5+
- match:
6+
dependency_type: production
7+
update_type: security:minor # includes patch updates!
8+
9+
- match:
10+
dependency_type: production
11+
update_type: semver:patch

‎.github/dependabot.yml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,12 +3,12 @@ updates:
33
- package-ecosystem: "github-actions"
44
directory: "/"
55
schedule:
6-
interval: "daily"
6+
interval: "weekly"
77
time: "08:00"
88
timezone: "America/Chicago"
99
labels:
1010
- ":robot: bot"
11-
# Set the access for individual scopes, or use permissions: write-all
11+
1212
permissions:
1313
pull-requests: write
1414
issues: write

0 commit comments

Comments
 (0)