Skip to content

Commit bbf1a7f

Browse files
Kai Kreuzerkaikreuzer
Kai Kreuzer
authored and
kaikreuzer
committed
Signed-off-by: Kai Kreuzer <[email protected]>
0 parents  commit bbf1a7f

File tree

302 files changed

+29726
-0
lines changed

Some content is hidden

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

302 files changed

+29726
-0
lines changed

‎.github/ISSUE_TEMPLATE/bug_report.md

+47
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
---
2+
name: "\U0001F41B Bug report"
3+
about: Something isn't working correctly with an add-on. This is the wrong place for user-interfaces or openHAB Core issues.
4+
labels: bug
5+
6+
---
7+
8+
<!-- Provide a general summary of the issue in the *Title* above -->
9+
<!-- If the issue is related to a binding, please include its short name in -->
10+
<!-- square brackets in the title - Example: "[astro] My issue..." -->
11+
12+
<!-- Important: Please contact the openHAB community forum for questions or -->
13+
<!-- for configuration and usage guidance: https://community.openhab.org -->
14+
15+
<!-- Feel free to delete any comment lines in the template (starting with "<!--") -->
16+
17+
## Expected Behavior
18+
<!-- If you're describing a bug, tell us what should happen -->
19+
<!-- If you're suggesting a change/improvement, tell us how it should work -->
20+
21+
## Current Behavior
22+
<!-- If describing a bug, tell us what happens instead of the expected behavior -->
23+
<!-- Include related log information (preferably debug level) and related configs -->
24+
<!-- Use a file attachment for log and config information longer than a few lines -->
25+
<!-- Enclose multi-line log/code snippets with ``` on new lines for proper formatting -->
26+
<!-- If suggesting a change/improvement, explain the difference from current behavior -->
27+
<!-- For improvements, discuss at community.openhab.org first and include link to topic -->
28+
29+
## Possible Solution
30+
<!-- Not obligatory, but suggest a fix/reason for the bug, -->
31+
<!-- or ideas how to implement the addition or change -->
32+
33+
## Steps to Reproduce (for Bugs)
34+
<!-- Provide a link to a live example, or an unambiguous set of steps to -->
35+
<!-- reproduce this bug. Include code to reproduce, if relevant -->
36+
1.
37+
2.
38+
39+
## Context
40+
<!-- How has this issue affected you? What are you trying to accomplish? -->
41+
<!-- Providing context helps us come up with a solution that is most useful in the real world -->
42+
43+
## Your Environment
44+
<!-- Include as many relevant details about the environment you experienced the bug in -->
45+
* Version used: (e.g., openHAB and add-on versions)
46+
* Environment name and version (e.g. Chrome 76, Java 8, Node.js 12.9, ...):
47+
* Operating System and version (desktop or mobile, Windows 10, Raspbian Buster, ...):

‎.github/ISSUE_TEMPLATE/documentation_issue.md

+17
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
name: "Documentation issue"
3+
about: Some information within the add-on documentation is wrong or missing
4+
labels: documentation
5+
6+
---
7+
<!-- Please report only add-on related documentation issues here -->
8+
<!-- Documentation issues within user interfaces or the core should be -->
9+
<!-- reported at https://github.com/openhab/openhab-docs/issues/new -->
10+
11+
<!-- Provide a general summary of the documentation issue in the *Title* above -->
12+
<!-- If the documentation issue is related to a specific add-on, please include its short name in -->
13+
<!-- square brackets in the title - Example: "[astro] My documentation issue..." -->
14+
15+
<!-- Important: Please contact the openHAB community forum for questions or -->
16+
<!-- for configuration and usage guidance: https://community.openhab.org -->
17+

‎.github/ISSUE_TEMPLATE/feature_request.md

+19
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
---
2+
name: "Feature request"
3+
about: You think that your favorite add-on should gain another feature
4+
labels: enhancement
5+
6+
---
7+
8+
<!-- Provide a general summary of the feature request in the *Title* above -->
9+
<!-- If the feature request is related to an add-on, please include its short name in -->
10+
<!-- square brackets in the title - Example: "[astro] My feature request..." -->
11+
12+
<!-- Important: Please contact the openHAB community forum for questions or -->
13+
<!-- for configuration and usage guidance: https://community.openhab.org -->
14+
15+
## Your Environment
16+
<!-- Include as many relevant details about the environment when applicable -->
17+
* Version used: (e.g., openHAB and add-on versions)
18+
* Environment name and version (e.g. Chrome 76, Java 8, Node.js 12.9, ...):
19+
* Operating System and version (desktop or mobile, Windows 10, Raspbian Buster, ...):

‎.github/ISSUE_TEMPLATE/usage_question.md

+10
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
name: "\U0001F914 Support/Usage Question"
3+
about: For usage questions, please use the openHAB community board!
4+
labels: question
5+
6+
---
7+
8+
This is an issue tracker for reporting problems and requesting new features. For usage questions, please use the openHAB community board where there are a lot more people ready to help you out. Thanks!
9+
10+
https://community.openhab.org/

‎.github/PULL_REQUEST_TEMPLATE.md

+62
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
<!--
2+
Thanks for contributing to the openHAB project!
3+
Please describe the goal and effect of your PR here.
4+
Pay attention to the below notes and to *the guidelines* for this repository.
5+
Feel free to delete any comment sections in the template (starting with "<!--").
6+
-->
7+
8+
<!-- TITLE -->
9+
10+
<!--
11+
Please provide a PR summary in the *Title* above, according to the following schema:
12+
- If related to one specific add-on: Mention the add-on shortname in square brackets
13+
e.g. "[exec]", "[netatmo]" or "[tesla]"
14+
- If the PR is work in progress: Add "[WIP]"
15+
- Give a short meaningful description in imperative mood
16+
e.g. "Add support for device XYZ" or "Fix wrongly handled exception"
17+
for a new add-on/binding: "Initial contribution"
18+
Examples:
19+
- "[homematic] Improve communication with weak signal devices"
20+
- "[timemachine][WIP] Initial contribution"
21+
- "Update contribution guidelines on new signing rules"
22+
-->
23+
24+
<!-- DESCRIPTION -->
25+
26+
<!--
27+
Please give a few sentences describing the overall goals of the pull request.
28+
Give enough details to make the improvement and changes of the PR understandable
29+
to both developers and tech-savy users.
30+
31+
Please keep the following in mind:
32+
- What is the classification of the PR, e.g. Bugfix, Improvement, Novel Addition, ... ?
33+
- Did you describe the PRs motivation and goal?
34+
- Did you provide a link to any prior discussion, e.g. an issue or community forum thread?
35+
- Did you describe new features for the end user?
36+
- Did you describe any noteworthy changes in usage for the end user?
37+
- Was the documentation updated accordingly, e.g. the add-on README?
38+
- Does your contribution follow the coding guidelines:
39+
https://www.openhab.org/docs/developer/development/guidelines.html
40+
- Did you check for any (relevant) issues from the static code analysis:
41+
https://www.openhab.org/docs/developer/development/bindings.html#static-code-analysis
42+
- Did you sign-off your work:
43+
https://www.openhab.org/docs/developer/contributing/contributing.html#sign-your-work
44+
-->
45+
46+
<!-- TESTING -->
47+
48+
<!--
49+
Your Pull Request will automatically be built and available under the following folder:
50+
https://openhab.jfrog.io/openhab/libs-pullrequest-local/org/openhab/
51+
52+
It is a good practice to add a URL to your built JAR in this Pull Request description,
53+
so it is easier for the community to test your Add-on.
54+
If your Pull Request contains a new binding, it will likely take some time
55+
before it is reviewed and processed by maintainers.
56+
That said, consider submitting your Add-on in the Eclipse IoT Marketplace
57+
See this thread for more info:
58+
https://community.openhab.org/t/24491
59+
60+
Don't forget to submit a thread about your Add-on in the openHAB community:
61+
https://community.openhab.org/c/add-ons
62+
-->

‎.gitignore

+23
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
.antlr*
2+
.idea
3+
.DS_Store
4+
*.iml
5+
npm-debug.log
6+
.build.log
7+
8+
.metadata/
9+
bin/
10+
target/
11+
src-gen/
12+
xtend-gen/
13+
.history/
14+
15+
*/plugin.xml_gen
16+
**/.settings/org.eclipse.*
17+
18+
bundles/**/src/main/history
19+
features/**/src/main/history
20+
features/**/src/main/feature
21+
22+
.vscode
23+
.factorypath

‎.travis.yml

+23
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
os: linux
2+
dist: focal
3+
4+
language: java
5+
jdk: openjdk11
6+
7+
cache:
8+
directories:
9+
- $HOME/.m2
10+
11+
before_cache:
12+
# remove resolver-status.properties, they change with each run and invalidate the cache
13+
- find $HOME/.m2 -name resolver-status.properties -exec rm {} \;
14+
15+
notifications:
16+
webhooks: https://www.travisbuddy.com/
17+
18+
travisBuddy:
19+
insertMode: update
20+
successBuildLog: true
21+
22+
install: true
23+
script: ./buildci.sh "$TRAVIS_COMMIT_RANGE"

0 commit comments

Comments
 (0)