From cfa4359b894fbe36c83e3b842b4471e61c16ef86 Mon Sep 17 00:00:00 2001 From: Marco Fabbroni Date: Tue, 5 Sep 2023 19:25:40 +0200 Subject: [PATCH 1/4] Update README.md Updated the "getting API key" section --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index b7368f5e..71344477 100644 --- a/README.md +++ b/README.md @@ -236,7 +236,7 @@ The component provides the following services: [See the Wiki](https://github.com/jeroenterheerdt/HAsmartirrigation/wiki/How-this-component-works). ## Getting Open Weather Map API key -Go to https://openweathermap.org and create an account. You can enter any company and purpose while creating an account. After creating your account, go to API Keys and get your key. If the key does not work right away, no worries. The email you should have received from OpenWeaterMap says it will be activated 'within the next couple of hours'. So if it does not work right away, be patient a bit. You will need to sign up for the paid (but free for limited API calls) OneCall API 3.0 plan if you do not have a key already. You can use a key for the 3.0 and 2.5 version of the API. +Go to https://openweathermap.org and create an account. You can enter any company and purpose while creating an account. After creating your account, You will need to sign up for the paid (but free for limited API calls) OneCall API 3.0 plan if you do not have a key already. Then, go to API Keys and get your key. If the key does not work right away, no worries. The email you should have received from OpenWeaterMap says it will be activated 'within the next couple of hours'. So if it does not work right away, be patient a bit. You can use a key for the 3.0 and 2.5 version of the API. If you are worried about the cost of the API, You can put a rate limit below the paid threshold in the "Billing plans" page of your profile. ## Getting Monthly ET values To get the monthly ET values use Rainmaster (US only), World Water & Climate Institute (worldwide) or another source that has this information for your area. From 6f8401cb7e2ef0f9fc3396f0192b176aada15147 Mon Sep 17 00:00:00 2001 From: Jeroen ter Heerdt Date: Wed, 13 Sep 2023 15:10:44 -0700 Subject: [PATCH 2/4] Create .gitvote.yml --- .github/.gitvote.yml | 155 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 155 insertions(+) create mode 100644 .github/.gitvote.yml diff --git a/.github/.gitvote.yml b/.github/.gitvote.yml new file mode 100644 index 00000000..d118cfea --- /dev/null +++ b/.github/.gitvote.yml @@ -0,0 +1,155 @@ +# GitVote configuration file +# +# GitVote will look for it in the following locations (in order of precedence): +# +# - At the root of the repository where the vote was created +# - At the root of the .github repository, for organization wide configuration +# + +# Automation (optional) +# +# Create votes automatically on PRs when any of the files affected by the PR +# match any of the patterns provided. Patterns must follow the gitignore +# format (https://git-scm.com/docs/gitignore#_pattern_format). +# +# Each automation rule must include a list of patterns and the profile to use +# when creating the vote. This allows creating votes automatically using the +# desired configuration based on the patterns matched. Rules are processed in +# the order provided, and the first match wins. +# +# automation: +# enabled: true +# rules: +# - patterns: +# - "README.md" +# - "*.txt" +# profile: default +# +automation: + enabled: false + rules: + - patterns: [] + profile: profile1 + +# Configuration profiles (required) +# +# A configuration profile defines some properties of a vote, like its duration, +# the pass threshold or the users who have a binding vote. It's possible to +# define multiple configuration profiles, each with a different set of settings. +# +profiles: + # Default configuration profile + # + # This profile will be used with votes created with the /vote command + default: + # Voting duration (required) + # + # How long the vote will be open + # + # Units supported (can be combined as in 1hour 30mins): + # + # minutes | minute | mins | min | m + # hours | hour | hrs | hrs | h + # days | day | d + # weeks | week | w + # + duration: 5m + + # Pass threshold (required) + # + # Percentage of votes in favor required to pass the vote + # + # The percentage is calculated based on the number of votes in favor and the + # number of allowed voters (see allowed_voters field below for more details). + pass_threshold: 50 + + # Allowed voters (optional) + # + # List of GitHub teams and users who have binding votes + # + # If no teams or users are provided, all repository collaborators will be + # allowed to vote. For organization-owned repositories, the list of + # collaborators includes outside collaborators, organization members that + # are direct collaborators, organization members with access through team + # memberships, organization members with access through default organization + # permissions, and organization owners. + # + # By default, teams' members with the maintainer role are allowed to vote + # as well. By using the `exclude_team_maintainers` option, it's possible to + # modify this behavior so that only teams' members with the member role are + # considered allowed voters. Please note that this option only applies to + # the teams explicitly listed in `allowed_voters/teams`. + # + # Teams names must be provided without the organization prefix. + # + # allowed_voters: + # teams: + # - team1 + # users: + # - cynthia-sg + # - tegioz + # exclude_team_maintainers: false + # + allowed_voters: + teams: [] + users: [] + + # Periodic status check + # + # GitVote allows checking the status of a vote in progress manually by + # calling the /check-vote command. The periodic status check option makes + # it possible to automate the execution of status checks periodically. The + # vote status will be published to the corresponding issue or pull request, + # the same way as if the /check-vote command would have been called + # manually. + # + # When this option is enabled, while the vote is open, a status check will + # be run automatically using the frequency configured. Please note that the + # hard limit of one status check per day still applies, so if the command + # has been called manually the automatic periodic run may be delayed. + # Automatic status checks won't be run if the vote will be closed within + # the next hour. + # + # Units supported: + # + # - day / days + # - week / weeks + # + # As an example, using a value of "5 days" would mean that 5 days after the + # vote was created, and every 5 days after that, an automatic status check + # will be run. + # + # periodic_status_check: "5 days" + # + periodic_status_check: null + + # Close on passing + # + # By default, votes remain open for the configured duration. Sometimes, + # specially on votes that stay open for a long time, it may be preferable + # to close a vote automatically once the passing threshold has been met. + # The close on passing feature makes this possible. Open votes where this + # feature has been enabled will be checked once daily and, if GitVote + # detects that the vote has passed, it will automatically close it. + # + # close_on_passing: true + # + close_on_passing: false + + # Additional configuration profiles + # + # In addition to the default configuration profile, it is possible to add more + # to easily create votes with different settings. To create a vote that uses a + # different profile you can use the command /vote-PROFILE. In the case below, + # the command would be /vote-profile1 + # + # Please note that each profile must contain all required fields. The default + # profile is used when using the /vote command, but its values are not used as + # default values when they are not provided on other profiles. + # + profile1: + duration: 1m + pass_threshold: 75 + allowed_voters: + teams: + - team1 From 18426c39dfc28ff20a41d50bdc3fe3990bc992c7 Mon Sep 17 00:00:00 2001 From: Jeroen ter Heerdt Date: Wed, 13 Sep 2023 15:12:00 -0700 Subject: [PATCH 3/4] Create .gitvote.yml --- .gitvote.yml | 155 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 155 insertions(+) create mode 100644 .gitvote.yml diff --git a/.gitvote.yml b/.gitvote.yml new file mode 100644 index 00000000..d118cfea --- /dev/null +++ b/.gitvote.yml @@ -0,0 +1,155 @@ +# GitVote configuration file +# +# GitVote will look for it in the following locations (in order of precedence): +# +# - At the root of the repository where the vote was created +# - At the root of the .github repository, for organization wide configuration +# + +# Automation (optional) +# +# Create votes automatically on PRs when any of the files affected by the PR +# match any of the patterns provided. Patterns must follow the gitignore +# format (https://git-scm.com/docs/gitignore#_pattern_format). +# +# Each automation rule must include a list of patterns and the profile to use +# when creating the vote. This allows creating votes automatically using the +# desired configuration based on the patterns matched. Rules are processed in +# the order provided, and the first match wins. +# +# automation: +# enabled: true +# rules: +# - patterns: +# - "README.md" +# - "*.txt" +# profile: default +# +automation: + enabled: false + rules: + - patterns: [] + profile: profile1 + +# Configuration profiles (required) +# +# A configuration profile defines some properties of a vote, like its duration, +# the pass threshold or the users who have a binding vote. It's possible to +# define multiple configuration profiles, each with a different set of settings. +# +profiles: + # Default configuration profile + # + # This profile will be used with votes created with the /vote command + default: + # Voting duration (required) + # + # How long the vote will be open + # + # Units supported (can be combined as in 1hour 30mins): + # + # minutes | minute | mins | min | m + # hours | hour | hrs | hrs | h + # days | day | d + # weeks | week | w + # + duration: 5m + + # Pass threshold (required) + # + # Percentage of votes in favor required to pass the vote + # + # The percentage is calculated based on the number of votes in favor and the + # number of allowed voters (see allowed_voters field below for more details). + pass_threshold: 50 + + # Allowed voters (optional) + # + # List of GitHub teams and users who have binding votes + # + # If no teams or users are provided, all repository collaborators will be + # allowed to vote. For organization-owned repositories, the list of + # collaborators includes outside collaborators, organization members that + # are direct collaborators, organization members with access through team + # memberships, organization members with access through default organization + # permissions, and organization owners. + # + # By default, teams' members with the maintainer role are allowed to vote + # as well. By using the `exclude_team_maintainers` option, it's possible to + # modify this behavior so that only teams' members with the member role are + # considered allowed voters. Please note that this option only applies to + # the teams explicitly listed in `allowed_voters/teams`. + # + # Teams names must be provided without the organization prefix. + # + # allowed_voters: + # teams: + # - team1 + # users: + # - cynthia-sg + # - tegioz + # exclude_team_maintainers: false + # + allowed_voters: + teams: [] + users: [] + + # Periodic status check + # + # GitVote allows checking the status of a vote in progress manually by + # calling the /check-vote command. The periodic status check option makes + # it possible to automate the execution of status checks periodically. The + # vote status will be published to the corresponding issue or pull request, + # the same way as if the /check-vote command would have been called + # manually. + # + # When this option is enabled, while the vote is open, a status check will + # be run automatically using the frequency configured. Please note that the + # hard limit of one status check per day still applies, so if the command + # has been called manually the automatic periodic run may be delayed. + # Automatic status checks won't be run if the vote will be closed within + # the next hour. + # + # Units supported: + # + # - day / days + # - week / weeks + # + # As an example, using a value of "5 days" would mean that 5 days after the + # vote was created, and every 5 days after that, an automatic status check + # will be run. + # + # periodic_status_check: "5 days" + # + periodic_status_check: null + + # Close on passing + # + # By default, votes remain open for the configured duration. Sometimes, + # specially on votes that stay open for a long time, it may be preferable + # to close a vote automatically once the passing threshold has been met. + # The close on passing feature makes this possible. Open votes where this + # feature has been enabled will be checked once daily and, if GitVote + # detects that the vote has passed, it will automatically close it. + # + # close_on_passing: true + # + close_on_passing: false + + # Additional configuration profiles + # + # In addition to the default configuration profile, it is possible to add more + # to easily create votes with different settings. To create a vote that uses a + # different profile you can use the command /vote-PROFILE. In the case below, + # the command would be /vote-profile1 + # + # Please note that each profile must contain all required fields. The default + # profile is used when using the /vote command, but its values are not used as + # default values when they are not provided on other profiles. + # + profile1: + duration: 1m + pass_threshold: 75 + allowed_voters: + teams: + - team1 From cc39c747c1e3969529c8a35220ed37311ed9f43a Mon Sep 17 00:00:00 2001 From: Jeroen ter Heerdt Date: Wed, 13 Sep 2023 15:13:32 -0700 Subject: [PATCH 4/4] Update .gitvote.yml --- .gitvote.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.gitvote.yml b/.gitvote.yml index d118cfea..7daf9ec6 100644 --- a/.gitvote.yml +++ b/.gitvote.yml @@ -53,7 +53,7 @@ profiles: # days | day | d # weeks | week | w # - duration: 5m + duration: 1w # Pass threshold (required) #