Skip to content

Commit 9c01af1

Browse files
aessingaessing
authored
Initial commit
0 parents  commit 9c01af1

20 files changed

+752
-0
lines changed

‎.github/CODEOWNERS

+43
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
# Explanation of this file
2+
# https://help.github.com/articles/about-codeowners/
3+
4+
* @aessing
5+
6+
###############################################################################
7+
# This is a comment.
8+
# Each line is a file pattern followed by one or more owners.
9+
10+
# These owners will be the default owners for everything in
11+
# the repo. Unless a later match takes precedence,
12+
# @global-owner1 and @global-owner2 will be requested for
13+
# review when someone opens a pull request.
14+
#* @global-owner1 @global-owner2
15+
16+
# Order is important; the last matching pattern takes the most
17+
# precedence. When someone opens a pull request that only
18+
# modifies JS files, only @js-owner and not the global
19+
# owner(s) will be requested for a review.
20+
#*.js @js-owner
21+
22+
# You can also use email addresses if you prefer. They'll be
23+
# used to look up users just like we do for commit author
24+
# emails.
25+
#*.go [email protected]
26+
27+
# In this example, @doctocat owns any files in the build/logs
28+
# directory at the root of the repository and any of its
29+
# subdirectories.
30+
#/build/logs/ @doctocat
31+
32+
# The `docs/*` pattern will match files like
33+
# `docs/getting-started.md` but not further nested files like
34+
# `docs/build-app/troubleshooting.md`.
35+
#docs/* [email protected]
36+
37+
# In this example, @octocat owns any file in an apps directory
38+
# anywhere in your repository.
39+
#apps/ @octocat
40+
41+
# In this example, @doctocat owns any file in the `/docs`
42+
# directory in the root of your repository.
43+
#/docs/ @doctocat

‎.github/FUNDING.yml

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
github: aessing

‎.github/ISSUE_TEMPLATE/BUG_REPORT_CRITICAL_TEMPLATE.md

+49
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
---
2+
name: Critical bug report
3+
about: Create a report for a critical issue
4+
title: ''
5+
labels: 'bug, critical'
6+
assignees: 'aessing'
7+
---
8+
9+
## Critical Bug Report
10+
11+
### Description
12+
13+
<!-- Please include a detailed summary to the issue itself, and why you consider it to be a bug. -->
14+
15+
### Expected Behavior
16+
17+
<!-- Please provide a description of the expected behavior. What should happen? -->
18+
19+
### Actual Behavior
20+
21+
<!-- Please provide a description of the actual behavior. What happens instead? -->
22+
23+
### Context
24+
25+
<!-- How has this issue affected you? What were you trying to accomplish? -->
26+
27+
### Steps to Reproduce
28+
29+
<!-- Please provide an unambiguous set of steps to reproduce this issue. If applicable, please include code to reproduce the issue. -->
30+
31+
1. Go to '...'
32+
2. Click on '....'
33+
3. Scroll down to '....'
34+
4. See error
35+
36+
### Your Environment
37+
38+
<!-- Please include as many relevant details as possible about your environment you experienced the issue in. -->
39+
40+
- Version used:
41+
- Environment name and version (e.g., Chrome 39, node.js 5.4):
42+
- Operating System and version:
43+
- Desktop or mobile:
44+
- Hardware used:
45+
- ...
46+
47+
### Screenshots
48+
49+
<!-- If applicable, please add screenshots to help explain the issue. -->

‎.github/ISSUE_TEMPLATE/BUG_REPORT_TEMPLATE.md

+49
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help to improve the project
4+
title: ''
5+
labels: 'bug'
6+
assignees: 'aessing'
7+
---
8+
9+
## Bug Report
10+
11+
### Description
12+
13+
<!-- Please include a detailed summary to the issue itself, and why you consider it to be a bug. -->
14+
15+
### Expected Behavior
16+
17+
<!-- Please provide a description of the expected behavior. What should happen? -->
18+
19+
### Actual Behavior
20+
21+
<!-- Please provide a description of the actual behavior. What happens instead? -->
22+
23+
### Context
24+
25+
<!-- How has this issue affected you? What were you trying to accomplish? -->
26+
27+
### Steps to Reproduce
28+
29+
<!-- Please provide an unambiguous set of steps to reproduce this issue. If applicable, please include code to reproduce the issue. -->
30+
31+
1. Go to '...'
32+
2. Click on '....'
33+
3. Scroll down to '....'
34+
4. See error
35+
36+
### Your Environment
37+
38+
<!-- Please include as many relevant details as possible about your environment you experienced the issue in. -->
39+
40+
- Version used:
41+
- Environment name and version (e.g., Chrome 39, node.js 5.4):
42+
- Operating System and version:
43+
- Desktop or mobile:
44+
- Hardware used:
45+
- ...
46+
47+
### Screenshots
48+
49+
<!-- If applicable, please add screenshots to help explain the issue. -->

‎.github/ISSUE_TEMPLATE/DOCUMENTATION_TEMPLATE.md

+33
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
---
2+
name: Documentation issue
3+
about: Report issues in the documentation or request an improvement
4+
title: ''
5+
labels: 'documentation'
6+
assignees: 'aessing'
7+
---
8+
9+
## Documentation Issue
10+
11+
### URL to the Article
12+
13+
<!-- Please provide the URL to the document that you report the issue for. -->
14+
15+
### Description
16+
17+
<!-- Please include a detailed summary of the request or to the issue itself. -->
18+
19+
### Expected Documentation
20+
21+
<!-- Please provide a description of the expected documentation. -->
22+
23+
### Actual Documentation
24+
25+
<!-- Please provide a description of the actual documentation. -->
26+
27+
### Context
28+
29+
<!-- How has this issue affected you? What were you trying to accomplish? -->
30+
31+
### Screenshots
32+
33+
<!-- If applicable, please add screenshots to help explain the issue. -->

‎.github/ISSUE_TEMPLATE/FEATURE_REQUEST_TEMPLATE.md

+25
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: 'feature'
6+
assignees: 'aessing'
7+
---
8+
9+
## Feature Request
10+
11+
### Description
12+
13+
<!-- Please include a detailed summary of the request or to the issue itself. -->
14+
15+
## Context
16+
17+
<!-- How has this issue affected you? What were you trying to accomplish? -->
18+
19+
### Expected Behavior
20+
21+
<!-- Please provide a description of the expected behavior. What should happen? -->
22+
23+
### Possible Implementation
24+
25+
<!-- Not obligatory, but please suggest an idea for implementing addition or change -->

‎.github/ISSUE_TEMPLATE/QUESTION_TEMPLATE.md

+11
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
name: Question
3+
about: You have a question about the project?
4+
title: ''
5+
labels: 'question'
6+
assignees: 'aessing'
7+
---
8+
9+
## Question
10+
11+
<!-- Please ask your question and provide as much detail as you can. If you have a question about a specific part of the project, please provide a link to the part of the project you are referring to. -->

‎.github/ISSUE_TEMPLATE/config.yml

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

‎.github/dependabot.yml

+21
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
version: 2
2+
updates:
3+
# Maintain dependencies for GitHub Actions
4+
- package-ecosystem: 'github-actions'
5+
directory: '/'
6+
schedule:
7+
interval: 'daily'
8+
time: '06:00'
9+
timezone: 'Europe/Berlin'
10+
assignees:
11+
- 'aessing'
12+
commit-message:
13+
prefix: 'Github Actions'
14+
include: 'scope'
15+
labels:
16+
- 'dependencies'
17+
open-pull-requests-limit: 10
18+
pull-request-branch-name:
19+
separator: '-'
20+
reviewers:
21+
- 'aessing'

‎.github/label-syncer/label-syncer.yml

+36
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
- name: breaking change
2+
description: Changes that will break something in the next release
3+
color: d876e3
4+
- name: bug
5+
description: Something isn't working as expected
6+
color: f67828
7+
- name: critical
8+
description: Problems that are critical to fix immediately (e.g. data loss)
9+
color: d80000
10+
- name: dependencies
11+
description: Pull requests that update a dependency
12+
color: 861a22
13+
- name: documentation
14+
description: Improvements or additions to documentation
15+
color: 0075ca
16+
- name: duplicate
17+
description: This issue or pull request already exists elsewhere
18+
color: D9D9D6
19+
- name: feature
20+
description: New feature or request for a feature
21+
color: f1dd38
22+
- name: help wanted
23+
description: Extra attention is needed
24+
color: 366735
25+
- name: idea
26+
description: An idea that should be considered for future releases
27+
color: 6aed9c
28+
- name: invalid
29+
description: This doesn't seem right
30+
color: 000000
31+
- name: question
32+
description: Further information is requested or clarification is needed
33+
color: 9d622b
34+
- name: wontfix
35+
description: This will not be worked on
36+
color: ffffff

‎.github/media/repository-open-graph-template.png

50.3 KB
Loading

‎.github/pull_request_template.md

+90
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,90 @@
1+
# Pull Request
2+
3+
## Description
4+
5+
<!-- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. -->
6+
7+
## Types of changes
8+
9+
What types of changes does your change introduce?</br>
10+
_Please put an `x` in the boxes that apply_
11+
12+
- [ ] New feature (adds functionality)
13+
- [ ] Bugfix (fixes an issue)
14+
- [ ] Security (fixes a security issue) | Please have a look at our [Security Policy](../docs/SECURITY.md) first.
15+
- [ ] Code style cleaning or Refactoring (formatting, renaming, restructuring, etc.)
16+
- [ ] Documentation Update
17+
- [ ] Other (please describe):
18+
19+
## Breaking changes
20+
21+
Does this Pull Request cause existing functionality to not work as expected or even break.</br>
22+
_Put an `x` in the boxes that apply_
23+
24+
- [ ] Yes
25+
- [ ] No
26+
27+
## How has the changes been tested?
28+
29+
<!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code. Please also provide instructions for how I can reproduce these tests. -->
30+
31+
- [ ] Test A
32+
- [ ] Test B
33+
34+
**Test Configuration(s)**:
35+
36+
- Hardware:
37+
- Firmware version:
38+
- Toolchain:
39+
- SDK:
40+
- ...
41+
42+
## Impacted Areas
43+
44+
<!-- Please list parts of the project that this Pull Request will affect: -->
45+
46+
- Area 1
47+
- Area 2
48+
- ...
49+
50+
## Related Issues
51+
52+
| Issue Name | Issue Number |
53+
| ----------------- | ---------------------------- |
54+
| FIRST ISSUE NAME | [#1](/user/project/issues/1) |
55+
| SECOND ISSUE NAME | [#2](/user/project/issues/2) |
56+
| ... | ... |
57+
58+
## Related Pull Requests
59+
60+
| Branch | Pull Request |
61+
| ---------------------------- | -------------------------- |
62+
| feature-ISSUENR-SHORTSUMMARY | [#1](/user/project/pull/1) |
63+
| fix-ISSUENR-SHORTSUMMARY | [#2](/user/project/pull/2) |
64+
| ... | ... |
65+
66+
<!--
67+
// feature - Create a capability e.g. feature, test, dependency.
68+
// remove - Remove a capability e.g. feature, test, dependency.
69+
// refactor - An update to existing code and/or refactoring.
70+
// fix - Fix an issue e.g. bug, typo, accident, misstatement.
71+
// bump - Increase the version of something e.g. dependency.
72+
// build - Change only to the build process, tooling, or infra.
73+
// document - A change to documentation only.
74+
// localize - String and localization only related changes.
75+
// revert - Reverting a previous commit.
76+
-->
77+
78+
## Checklist
79+
80+
Thank you for your contribution. Please review the following checklist before submitting your Pull Request.</br>
81+
_Please put an `x` in the boxes that apply_
82+
83+
- [ ] I reviewed the [guidelines for contributing](../docs/CONTRIBUTING.md) to this repository
84+
- [ ] I created an issue, or used an existing issue which is related to this Pull Request
85+
- [ ] I have performed a self-review of my own code
86+
- [ ] My code builds clean without any errors or warnings
87+
- [ ] My code follows the style guidelines of this project
88+
- [ ] I have commented my code, particularly in hard-to-understand areas
89+
- [ ] I have added necessary documentation (if appropriate)
90+
- [ ] I have added unit tests that prove my fix is effective or that my feature works

‎.github/workflows/label-syncer.yml

+25
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
name: Label Syncer
2+
on:
3+
workflow_dispatch:
4+
push:
5+
branches:
6+
- main
7+
paths:
8+
- .github/label-syncer/label-syncer.yml
9+
10+
jobs:
11+
build:
12+
name: Sync repository labels from file
13+
runs-on: ubuntu-latest
14+
steps:
15+
- name: Checkout Code
16+
id: checkout-code
17+
uses: actions/checkout@v3
18+
- name: Sync repository labels from file
19+
id: labeling
20+
uses: micnncim/action-label-syncer@v1
21+
if: success()
22+
env:
23+
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
24+
with:
25+
manifest: .github/label-syncer/label-syncer.yml

0 commit comments

Comments
 (0)