Skip to content

Commit bcfd855

Browse files
tuxthebottuxthebot
authored
Initial commit
0 parents  commit bcfd855

33 files changed

Lines changed: 3997 additions & 0 deletions

‎.github/CODEOWNERS‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
# These owners will be the default owners for everything in
2+
# the repo. Unless a later match takes precedence,
3+
# @Josee9988 will be requested for
4+
# review when someone opens a pull request.
5+
# if you want to add more owners, just write it after @Josee9988
6+
* @TuxTechLab

‎.github/CODE_OF_CONDUCT.md‎

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 make 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 behaviour 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 behaviour 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+
behaviour and are expected to take appropriate and fair corrective action in
38+
response to any instances of unacceptable behaviour.
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 behaviours 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 behaviour may be
58+
reported by contacting the project team at jgracia9988@gmail.com. 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 concerning 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>

‎.github/CONTRIBUTING.md‎

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
# **Contributing**
2+
3+
When contributing to this repository, please first discuss the change you wish to make via issue,
4+
email, or any other method with the owners of this repository before making a change.
5+
6+
Please note we have a [code of conduct](CODE_OF_CONDUCT.md); please follow it in all your interactions with the project.
7+
8+
## Pull Request Process
9+
10+
1. Ensure any install or build dependencies are removed before the end of the layer when doing a
11+
build.
12+
2. Update the README.md with details of changes to the interface; this includes new environment variables, exposed ports, valid file locations and container parameters.
13+
3. Increase the version numbers in any examples files and the README.md to the new version that this
14+
Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
15+
4. You may merge the Pull Request once you have the sign-off of two other developers, or if you
16+
do not have permission to do that, you may request the second reviewer to merge it for you.
17+
18+
## Issue Report Process
19+
20+
1. Go to the project's issues.
21+
2. Select the template that better fits your issue.
22+
3. Read the instructions carefully and write within the template guidelines.
23+
4. Submit it and wait for support.

‎.github/FUNDING.yml‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
github: TuxTechLab
2+
custom: ['https://www.paypal.me/TuxTechLab']

‎.github/ISSUE_TEMPLATE.md‎

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
<!--📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛
2+
3+
Oh, hi there! 😄
4+
5+
To make our work more accessible, we recommend you to choose any of our available issue templates rather than using (this) a blank template.
6+
7+
To expedite issue processing, please search open and closed issues before submitting a new one.
8+
Please read our Rules of Conduct at this repository's `.github/CODE_OF_CONDUCT.md`
9+
10+
📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛-->
11+
12+
# **Blank Issue Report**
13+
14+
## **Describe the issue**
15+
<!-- A clear and concise description of the problem. -->
16+
17+
*
18+
19+
---
20+
21+
### **Media prove**
22+
<!-- If applicable, add screenshots or videos to help explain your problem. -->
23+
24+
---
25+
26+
### **Your environment**
27+
28+
<!-- use all the applicable bulleted list elements for this specific issue,
29+
and remove all the bulleted list elements that are not relevant for this issue. -->
30+
31+
* OS: <!--[e.g. Ubuntu 5.4.0-26-generic x86_64 / Windows 1904 ...]-->
32+
* Node version:
33+
* Npm version:
34+
* Browser name and version:
35+
36+
---
37+
38+
### **Additional context**
39+
<!-- Add any other context or additional information about the issue here.-->
40+
41+
*

‎.github/ISSUE_TEMPLATE/1-bug-report.md‎

Lines changed: 79 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,79 @@
1+
---
2+
name: "🐞 Bug Report"
3+
about: "Report an issue to help the project improve."
4+
title: "[Bug] "
5+
labels: "Type: Bug"
6+
assignees: Tux
7+
8+
---
9+
10+
# **🐞 Bug Report**
11+
12+
## **Describe the bug**
13+
<!-- A clear and concise description of what the bug is. -->
14+
15+
*
16+
17+
---
18+
19+
### **Is this a regression?**
20+
<!-- Did this behaviour used to work in the previous version? -->
21+
<!-- Yes, the last version in which this bug was not present was: ... -->
22+
23+
---
24+
25+
### **To Reproduce**
26+
27+
<!-- Steps to reproduce the error:
28+
(e.g.:)
29+
1. Use x argument / navigate to
30+
2. Fill this information
31+
3. Go to...
32+
4. See error -->
33+
34+
<!-- Write the steps here (add or remove as many steps as needed)-->
35+
36+
1.
37+
2.
38+
3.
39+
4.
40+
41+
---
42+
43+
### **Expected behaviour**
44+
<!-- A clear and concise description of what you expected to happen. -->
45+
46+
*
47+
48+
---
49+
50+
### **Media prove**
51+
<!-- If applicable, add screenshots or videos to help explain your problem. -->
52+
53+
---
54+
55+
### **Your environment**
56+
57+
<!-- use all the applicable bulleted list elements for this specific issue,
58+
and remove all the bulleted list elements that are not relevant for this issue. -->
59+
60+
* OS: <!--[e.g. Ubuntu 5.4.0-26-generic x86_64 / Windows 1904 ...]-->
61+
* Node version:
62+
* Npm version:
63+
* Browser name and version:
64+
65+
---
66+
67+
### **Additional context**
68+
<!-- Add any other context or additional information about the problem here.-->
69+
70+
*
71+
72+
<!--📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛
73+
74+
Oh, hi there! 😄
75+
76+
To expedite issue processing, please search open and closed issues before submitting a new one.
77+
Please read our Rules of Conduct at this repository's `.github/CODE_OF_CONDUCT.md`
78+
79+
📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛-->

‎.github/ISSUE_TEMPLATE/2-failing-test.md‎

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
name: "💉 Failing Test"
3+
about: "Report failing tests or CI jobs."
4+
title: "[Test] "
5+
labels: "Type: Test"
6+
assignees: Tux
7+
8+
---
9+
10+
# **💉 Failing Test**
11+
12+
## **Which jobs/test(s) are failing**
13+
<!-- The CI jobs or tests that are failing -->
14+
15+
*
16+
17+
---
18+
19+
## **Reason for failure/description**
20+
<!-- Try to describe why the test is failing or what we are missing to make it pass. -->
21+
22+
---
23+
24+
### **Media prove**
25+
<!-- If applicable, add screenshots or videos to help explain your problem. -->
26+
27+
---
28+
29+
### **Additional context**
30+
<!-- Add any other context or additional information about the problem here. -->
31+
32+
*
33+
34+
<!--📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛
35+
36+
Oh, hi there! 😄
37+
38+
To expedite issue processing, please search open and closed issues before submitting a new one.
39+
Please read our Rules of Conduct at this repository's `.github/CODE_OF_CONDUCT.md`
40+
41+
📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛-->

‎.github/ISSUE_TEMPLATE/3-docs-bug.md‎

Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
---
2+
name: "📚 Documentation or README.md issue report"
3+
about: "Report an issue in the project's documentation or README.md file."
4+
title: ""
5+
labels: "Documentation"
6+
assignees: Tux
7+
8+
---
9+
# **📚 Documentation Issue Report**
10+
11+
## **Describe the bug**
12+
<!-- A clear and concise description of what the bug is. -->
13+
14+
*
15+
16+
---
17+
18+
### **To Reproduce**
19+
20+
<!-- Steps to reproduce the error:
21+
(e.g.:)
22+
1. Use x argument / navigate to
23+
2. Fill this information
24+
3. Go to...
25+
4. See error -->
26+
27+
<!-- Write the steps here (add or remove as many steps as needed)-->
28+
29+
1.
30+
2.
31+
3.
32+
4.
33+
34+
---
35+
36+
### **Media prove**
37+
<!-- If applicable, add screenshots or videos to help explain your problem. -->
38+
39+
---
40+
41+
## **Describe the solution you'd like**
42+
<!-- A clear and concise description of what you want to happen. -->
43+
44+
*
45+
46+
---
47+
48+
### **Additional context**
49+
<!-- Add any other context or additional information about the problem here.-->
50+
51+
*
52+
53+
<!--📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛
54+
55+
Oh, hi there! 😄
56+
57+
To expedite issue processing, please search open and closed issues before submitting a new one.
58+
Please read our Rules of Conduct at this repository's `.github/CODE_OF_CONDUCT.md`
59+
60+
📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛-->

‎.github/ISSUE_TEMPLATE/4-feature-request.md‎

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
name: "🚀🆕 Feature Request"
3+
about: "Suggest an idea or possible new feature for this project."
4+
title: ""
5+
labels: "Type: Feature"
6+
assignees: Tux
7+
---
8+
9+
# **🚀 Feature Request**
10+
11+
## **Is your feature request related to a problem? Please describe.**
12+
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
13+
14+
*
15+
16+
---
17+
18+
## **Describe the solution you'd like**
19+
<!-- A clear and concise description of what you want to happen. -->
20+
21+
*
22+
23+
---
24+
25+
## **Describe alternatives you've considered**
26+
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
27+
28+
*
29+
30+
---
31+
32+
### **Additional context**
33+
<!-- Add any other context or additional information about the problem here.-->
34+
35+
*
36+
37+
<!--📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛
38+
39+
Oh, hi there! 😄
40+
41+
To expedite issue processing, please search open and closed issues before submitting a new one.
42+
Please read our Rules of Conduct at this repository's `.github/CODE_OF_CONDUCT.md`
43+
44+
📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛📛-->

0 commit comments

Comments
 (0)