Skip to content

Commit d663e02

Browse files
committed
merging
2 parents 7af5fad + 0493da6 commit d663e02

File tree

6 files changed

+190
-11
lines changed

6 files changed

+190
-11
lines changed

.github/ISSUE_TEMPLATE/config.yml

Lines changed: 0 additions & 8 deletions
This file was deleted.

boards.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
menu.softdevice=SoftDevice
2-
menu.debug=Debug Level
3-
menu.debug_output=Debug Port
2+
menu.debug=Debug
3+
menu.debug_output=Debug Output
44

55
# ----------------------------------
66
# SuperMini nRF52840

libraries/Adafruit_TinyUSB_Arduino

Submodule Adafruit_TinyUSB_Arduino deleted from d629476
Lines changed: 92 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,92 @@
1+
name: Bug Report
2+
description: Report a problem with TinyUSB Library
3+
labels: 'Bug'
4+
body:
5+
- type: markdown
6+
attributes:
7+
value: |
8+
Thanks for taking the time to fill out this bug report!
9+
It's okay to leave some blank if it doesn't apply to your problem.
10+
11+
- type: dropdown
12+
attributes:
13+
label: Operating System
14+
options:
15+
- Linux
16+
- MacOS
17+
- RaspberryPi OS
18+
- Windows 7
19+
- Windows 10
20+
- Windows 11
21+
- Others
22+
validations:
23+
required: true
24+
25+
- type: input
26+
attributes:
27+
label: IDE version
28+
placeholder: e.g Arduino 1.8.15
29+
validations:
30+
required: true
31+
32+
- type: input
33+
attributes:
34+
label: Board
35+
placeholder: e.g Feather nRF52840 Express
36+
validations:
37+
required: true
38+
39+
- type: input
40+
attributes:
41+
label: BSP version
42+
description: Can be found under "Board Manager" menu
43+
validations:
44+
required: true
45+
46+
- type: input
47+
attributes:
48+
label: TinyUSB Library version
49+
placeholder: "Release version or github latest"
50+
validations:
51+
required: true
52+
53+
- type: textarea
54+
attributes:
55+
label: Sketch
56+
placeholder: |
57+
e.g examples/MassStorage/msc_ramdisk.
58+
If it is custom sketch, please provide it as **ATTACHED** files or link to it.
59+
validations:
60+
required: true
61+
62+
- type: textarea
63+
attributes:
64+
label: What happened ?
65+
placeholder: A clear and concise description of what the bug is.
66+
validations:
67+
required: true
68+
69+
- type: textarea
70+
attributes:
71+
label: How to reproduce ?
72+
placeholder: |
73+
1. Go to '...'
74+
2. Click on '....'
75+
3. See error
76+
validations:
77+
required: true
78+
79+
- type: textarea
80+
attributes:
81+
label: Debug Log
82+
placeholder: |
83+
TinyUSB debug log where the issue occurred as attached txt file, best with comments to explain the actual events.
84+
validations:
85+
required: false
86+
87+
- type: textarea
88+
attributes:
89+
label: Screenshots
90+
description: If applicable, add screenshots to help explain your problem.
91+
validations:
92+
required: false
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: "[Feature]"
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.
Lines changed: 76 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as
6+
contributors and maintainers pledge to making participation in our project and
7+
our community a harassment-free experience for everyone, regardless of age, body
8+
size, disability, ethnicity, sex characteristics, gender identity and expression,
9+
level of experience, education, socio-economic status, nationality, personal
10+
appearance, race, religion, or sexual identity and orientation.
11+
12+
## Our Standards
13+
14+
Examples of behavior that contributes to creating a positive environment
15+
include:
16+
17+
* Using welcoming and inclusive language
18+
* Being respectful of differing viewpoints and experiences
19+
* Gracefully accepting constructive criticism
20+
* Focusing on what is best for the community
21+
* Showing empathy towards other community members
22+
23+
Examples of unacceptable behavior by participants include:
24+
25+
* The use of sexualized language or imagery and unwelcome sexual attention or
26+
advances
27+
* Trolling, insulting/derogatory comments, and personal or political attacks
28+
* Public or private harassment
29+
* Publishing others' private information, such as a physical or electronic
30+
address, without explicit permission
31+
* Other conduct which could reasonably be considered inappropriate in a
32+
professional setting
33+
34+
## Our Responsibilities
35+
36+
Project maintainers are responsible for clarifying the standards of acceptable
37+
behavior and are expected to take appropriate and fair corrective action in
38+
response to any instances of unacceptable behavior.
39+
40+
Project maintainers have the right and responsibility to remove, edit, or
41+
reject comments, commits, code, wiki edits, issues, and other contributions
42+
that are not aligned to this Code of Conduct, or to ban temporarily or
43+
permanently any contributor for other behaviors that they deem inappropriate,
44+
threatening, offensive, or harmful.
45+
46+
## Scope
47+
48+
This Code of Conduct applies both within project spaces and in public spaces
49+
when an individual is representing the project or its community. Examples of
50+
representing a project or community include using an official project e-mail
51+
address, posting via an official social media account, or acting as an appointed
52+
representative at an online or offline event. Representation of a project may be
53+
further defined and clarified by project maintainers.
54+
55+
## Enforcement
56+
57+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
58+
reported by contacting the project team at . All
59+
complaints will be reviewed and investigated and will result in a response that
60+
is deemed necessary and appropriate to the circumstances. The project team is
61+
obligated to maintain confidentiality with regard to the reporter of an incident.
62+
Further details of specific enforcement policies may be posted separately.
63+
64+
Project maintainers who do not follow or enforce the Code of Conduct in good
65+
faith may face temporary or permanent repercussions as determined by other
66+
members of the project's leadership.
67+
68+
## Attribution
69+
70+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71+
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
72+
73+
[homepage]: https://www.contributor-covenant.org
74+
75+
For answers to common questions about this code of conduct, see
76+
https://www.contributor-covenant.org/faq

0 commit comments

Comments
 (0)