Skip to content

Commit 8e5654c

Browse files
lukasmasuchlukasmasuch
committed
Commit initial version
1 parent 116e8b6 commit 8e5654c

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

53 files changed

+5003
-0
lines changed

‎.devcontainer/devcontainer.json

+42
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
{
2+
"name": "build-environment",
3+
"build": {
4+
"dockerfile": "../.github/actions/build-environment/Dockerfile"
5+
},
6+
7+
// Set *default* container specific settings.json values on container create.
8+
"settings": {
9+
"terminal.integrated.shell.linux": "/bin/bash"
10+
},
11+
12+
// Add the IDs of extensions you want installed when the container is created.
13+
"extensions": [
14+
// General Development
15+
"esbenp.prettier-vscode",
16+
"EditorConfig.EditorConfig",
17+
"mutantdino.resourcemonitor",
18+
"redhat.vscode-yaml",
19+
// Collaboration
20+
"eamodio.gitlens",
21+
// Markdown
22+
"DavidAnson.vscode-markdownlint",
23+
// Python Development
24+
"ms-python.python",
25+
"ms-python.vscode-pylance",
26+
]
27+
28+
// Use 'forwardPorts' to make a list of ports inside the container available locally.
29+
// :3000 for the React Webapp started via `yarn run`
30+
// "forwardPorts": [ 3000 ]
31+
32+
// Use 'postCreateCommand' to run commands after the container is created.
33+
// "postCreateCommand": "uname -a",
34+
// or postStartCommand
35+
36+
// Uncomment when using a ptrace-based debugger like C++, Go, and Rust
37+
// "runArgs": [ "--cap-add=SYS_PTRACE", "--security-opt", "seccomp=unconfined" ],
38+
39+
// Uncomment to connect as a non-root user. See https://aka.ms/vscode-remote/containers/non-root.
40+
// "remoteUser": "vscode"
41+
42+
}

‎.editorconfig

+23
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
# http://editorconfig.org
2+
3+
root = true
4+
5+
[*]
6+
charset = utf-8
7+
end_of_line = lf
8+
indent_style = space
9+
trim_trailing_whitespace = true
10+
insert_final_newline = true
11+
12+
[*.md]
13+
max_line_length = off
14+
trim_trailing_whitespace = false
15+
16+
[*.py]
17+
indent_size = 4
18+
19+
[*.json]
20+
indent_size = 2
21+
22+
[*.{yaml,yml}]
23+
indent_size = 2

‎.github/CODEOWNERS

+8
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
# This file provides an overview of code owners in this repository.
2+
3+
# Each line is a file pattern followed by one or more owners.
4+
# The last matching pattern has the most precedence.
5+
# For more details, read the following article on GitHub: https://help.github.com/articles/about-codeowners/.
6+
7+
# These are the default owners for the whole content of this repository. The default owners are automatically added as reviewers when you open a pull request, unless different owners are specified in the file.
8+
* @LukasMasuch @raethlein @JanKalkan

‎.github/CODE_OF_CONDUCT.md

+76
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 [email protected]. 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

‎.github/ISSUE_TEMPLATE/01_bug-report.md

+44
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
name: "\U0001F6A8 Bug Report"
3+
about: Did you come across a bug or unexpected behaviour differing from the docs?
4+
title: ''
5+
labels: bug
6+
assignees: ''
7+
8+
---
9+
<!--
10+
Thanks for reporting a bug 🙌 ❤️
11+
12+
Before opening a new issue, please make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead. Also, be sure to check our documentation first.
13+
-->
14+
15+
**Describe the bug:**
16+
17+
<!-- Describe your issue, but please be descriptive! Thanks again 🙌 ❤️ -->
18+
19+
**Expected behaviour:**
20+
21+
<!-- A clear and concise description of what you expected to happen. -->
22+
23+
**Steps to reproduce the issue:**
24+
25+
<!-- include screenshots, logs, code or other info to help explain your problem.
26+
27+
1. Go to '...'
28+
2. Click on '....'
29+
3. Scroll down to '....'
30+
4. See error
31+
-->
32+
33+
**Technical details:**
34+
35+
- Host Machine OS (Windows/Linux/Mac):
36+
- Browser (Chrome/Firefox/Safari):
37+
38+
**Possible Fix:**
39+
40+
<!--- Not obligatory, but suggest a fix or reason for the bug -->
41+
42+
**Additional context:**
43+
44+
<!-- Add any other context about the problem here. -->

‎.github/ISSUE_TEMPLATE/02_feature_request.md

+31
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
---
2+
name: "\U0001F381 Feature Request"
3+
about: Do you have an idea for an improvement or a new feature?
4+
title: ''
5+
labels: feature
6+
assignees: ''
7+
8+
---
9+
<!--
10+
Thanks for requesting a feature 🙌 ❤️
11+
12+
Before opening a new issue, please make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead. Also, be sure to check our documentation first.
13+
-->
14+
15+
**Feature description:**
16+
17+
<!---
18+
Provide a detailed description of the feature or improvement you are proposing. What specific solution would you like? What is the expected behaviour?
19+
20+
Add any other context, screenshots, or code snippets about the feature request here as well.
21+
-->
22+
23+
**Problem and motivation:**
24+
25+
<!---
26+
Why is this change important to you? What is the problem this feature would solve? How would you use it? How can it benefit other users?
27+
-->
28+
29+
**Is this something you're interested in working on?**
30+
31+
<!--- Yes or No -->

‎.github/ISSUE_TEMPLATE/03_documentation.md

+16
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
name: "\U0001F4DD Documentation"
3+
about: Is there a mistake in the docs, is anything unclear or do you have a suggestion?
4+
title: ''
5+
labels: documentation
6+
assignees: ''
7+
8+
---
9+
10+
**Describe your request:**
11+
12+
<!-- Describe the problem or suggestion here. If you've found a mistake and you know the answer, feel free to submit a pull request straight away. -->
13+
14+
**Which page or section is this issue related to?**
15+
16+
<!-- Please include the URL. -->

‎.github/ISSUE_TEMPLATE/04_deployment-problem.md

+23
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
name: "\U0001F433 Deployment Problem"
3+
about: Do you have problems with deployment, and none of the suggestions in the docs helped?
4+
title: ''
5+
labels: 'support'
6+
assignees: ''
7+
8+
---
9+
10+
<!--
11+
Thanks for reporting an issue with deployment 🙌 ❤️
12+
13+
Before opening a new issue, please make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead. Also, be sure to check our documentation first.
14+
-->
15+
16+
**Describe the issue:**
17+
18+
<!-- Describe your issue, but please be descriptive! Include screenshots, logs, code or other info to help explain your problem -->
19+
20+
**Technical details:**
21+
22+
- Host Machine OS (Windows/Linux/Mac):
23+
- Browser (Chrome/Firefox/Safari):

‎.github/ISSUE_TEMPLATE/05_other.md

+13
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
name: "\U0001F4AC Anything else?"
3+
about: 'Do you have any other question?'
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
<!--
10+
Thanks for contributing to the project 🙌 ❤️
11+
12+
Before opening a new issue, please make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead. Also, be sure to check our readme first.
13+
-->

‎.github/ISSUE_TEMPLATE/config.yml

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
blank_issues_enabled: true

‎.github/PULL_REQUEST_TEMPLATE.md

+19
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
**What kind of change does this PR introduce?**
2+
3+
<!-- (Update "[ ]" to "[x]" to check a box) -->
4+
5+
- [ ] Bugfix
6+
- [ ] New Feature
7+
- [ ] Feature Improvment
8+
- [ ] Refactoring
9+
- [ ] Documentation
10+
- [ ] Other, please describe:
11+
12+
**Description:**
13+
<!--- Use this section to describe your changes. Why is this change required? What problem does it solve? If your test fixes a specific issue, don't forget to reference the issue number. If your PR is still a work in progress, that's totally fine – just include [WIP] within the title. -->
14+
15+
**Checklist:**
16+
<!--- Before you submit the PR, go over this checklist and make sure you can tick off all the boxes. [] -> [x] -->
17+
18+
- [ ] I have read the [CONTRIBUTING](../CONTRIBUTING.md) document.
19+
- [ ] My changes don't require a change to the documentation, or if they do, I've added all required information.

‎.github/SUPPORT.md

+3
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
# Support
2+
3+
Please refer to our [support](../../../#support) and [contribution](../../../#contribution) sections on our main README for more information.

‎.github/actions/build-environment/Dockerfile

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
FROM mltooling/build-environment:0.4.2

‎.github/actions/build-environment/action.yml

+23
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
name: "build-environment"
2+
description: "Environment to run build, test, check, and release steps."
3+
author: "ML Tooling <[email protected]>"
4+
inputs:
5+
build_args:
6+
description: "Build arguments passed to the build.py scripts"
7+
required: false
8+
working_directory:
9+
description: "Working directory from where the build command is run"
10+
required: false
11+
container_registry_url:
12+
description: "URL used for container registry login"
13+
required: false
14+
container_registry_username:
15+
description: "Username used for container registry login"
16+
required: false
17+
container_registry_password:
18+
description: "Password used for container registry login"
19+
required: false
20+
21+
runs:
22+
using: "docker"
23+
image: "Dockerfile"

‎.github/pr-labeler-branch-prefix.yml

+5
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
feature: ["feature/*", "feat/*", "enhancement/*"]
2+
bug: ["bugfix/*", "fix/*"]
3+
maintenance: ["maintenance/*", "chore/*", "refactoring/*", "test/*", "style/*"]
4+
documentation: ["documentation/*", "docs/*"]
5+
security: ["security/*"]

‎.github/pr-labeler-file-path.yml

+20
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
# Add documentation label to any change in documentation related files
2+
documentation:
3+
- "docs/*"
4+
- "docs/**/*"
5+
- "README.md"
6+
- "**/README.md"
7+
- "CONTRIBUTING.md"
8+
9+
maintenance:
10+
- ".vscode/*"
11+
- ".vscode/**/*"
12+
- ".github/*"
13+
- ".github/**/*"
14+
- ".reuse/*"
15+
- "LICENSES/*"
16+
- ".editorconfig"
17+
- ".gitignore"
18+
- "**/.gitignore"
19+
- "build.py"
20+
- "**/build.py"

0 commit comments

Comments
 (0)