unirpi-io 0.0.2 → 0.0.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +5 -2
- package/CODE_OF_CONDUCT.md +0 -12
- package/CONTRIBUTING.md +0 -33
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "unirpi-io",
|
|
3
|
-
"version": "0.0.
|
|
3
|
+
"version": "0.0.6",
|
|
4
4
|
"description": "A mock implementation of RPI-IO (by gdorbes) to use a fake instance of Raspberry Pi GPIO's on any platform for Node.js",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"unirpi-io",
|
|
@@ -25,7 +25,10 @@
|
|
|
25
25
|
"publishConfig": {
|
|
26
26
|
"access": "public"
|
|
27
27
|
},
|
|
28
|
+
"files": [
|
|
29
|
+
"index.js"
|
|
30
|
+
],
|
|
28
31
|
"scripts": {
|
|
29
|
-
"test": "echo \"
|
|
32
|
+
"test": "echo \"No tests specified yet\""
|
|
30
33
|
}
|
|
31
34
|
}
|
package/CODE_OF_CONDUCT.md
DELETED
|
@@ -1,12 +0,0 @@
|
|
|
1
|
-
## Code of Conduct
|
|
2
|
-
|
|
3
|
-
As a contributor to this project, you are expected to adhere to the following code of conduct:
|
|
4
|
-
|
|
5
|
-
- Be respectful, kind, and patient
|
|
6
|
-
- Welcome feedback constructively
|
|
7
|
-
- Avoid offensive or discriminatory language
|
|
8
|
-
- Focus on collaboration
|
|
9
|
-
- Properly credit contributors
|
|
10
|
-
- Report concerns privately
|
|
11
|
-
|
|
12
|
-
Failure to adhere to this code of conduct may result in removal from the project and reporting to GitHub if necessary.
|
package/CONTRIBUTING.md
DELETED
|
@@ -1,33 +0,0 @@
|
|
|
1
|
-
# Contributing
|
|
2
|
-
|
|
3
|
-
Anyone is welcome to contribute to this project.
|
|
4
|
-
Please make sure to follow these steps thoroughly to contribute :
|
|
5
|
-
|
|
6
|
-
1. **Fork the repository:** Click the Fork button on GitHub to create your copy.
|
|
7
|
-
|
|
8
|
-
2. **Clone your fork:**
|
|
9
|
-
```bash
|
|
10
|
-
git clone https://github.com/your-username/your-fork.git
|
|
11
|
-
```
|
|
12
|
-
|
|
13
|
-
3. **Create a branch for your feature:**
|
|
14
|
-
```bash
|
|
15
|
-
git checkout -b feat/your-feature
|
|
16
|
-
```
|
|
17
|
-
|
|
18
|
-
4. **Set up the environment:** Follow the setup instructions in the README.
|
|
19
|
-
|
|
20
|
-
5. **Use clear commit messages:**
|
|
21
|
-
- `feat:` – New feature
|
|
22
|
-
- `fix:` – Bug fix
|
|
23
|
-
- `docs:` – Documentation update
|
|
24
|
-
- `refactor:` – Code restructuring
|
|
25
|
-
|
|
26
|
-
6. **Submit a Pull Request (PR):**
|
|
27
|
-
|
|
28
|
-
Include:
|
|
29
|
-
- Description of the changes
|
|
30
|
-
- References to issues (e.g., Closes #12)
|
|
31
|
-
- Screenshots or examples (if applicable)
|
|
32
|
-
|
|
33
|
-
7. **Participate in the code review:** Be collaborative and responsive.
|