Skip to content

Commit

Permalink
chore: Add Fleet API warning (#926)
Browse files Browse the repository at this point in the history
* Update issue_car.yml

Try and reduce API readonly issues being raised with non-fleet api

* style: auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

---------

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: Alan Tse <[email protected]>
  • Loading branch information
3 people authored Mar 23, 2024
1 parent e55e472 commit e531317
Showing 1 changed file with 10 additions and 2 deletions.
12 changes: 10 additions & 2 deletions .github/ISSUE_TEMPLATE/issue_car.yml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
name: Telsa Car Issue
description: Create a report to help us improve
title: "Car Issue: "
title: "Car: "
labels: ["triage", "car"]
body:
- type: checkboxes
Expand All @@ -10,6 +10,14 @@ body:
options:
- label: I have searched both the existing open issues & recently closed issues and did not find a duplicate of this issue.
required: true
- type: checkboxes
attributes:
label: I have read about the [Fleet API](https://github.com/alandtse/tesla?tab=readme-ov-file#tesla-fleet-api-proxy) and understand I may need to use it
description: Unless you have a Pre-2021 Model S/X the Fleet API will need to be used for all other vehicles in the future.
options:
- label: I understand issues relating to read only commands will be auto closed if not using the Fleet API.
required: true

- type: markdown
attributes:
value: |
Expand Down Expand Up @@ -61,7 +69,7 @@ body:
description: Enable the debug logs ([In Home Assistant](https://my.home-assistant.io/redirect/integration/?domain=tesla_custom) & click `Enable debug logging`)
render: true
placeholder: |
Your logs here
Your logs here, please follow the instructions above - https://my.home-assistant.io/redirect/integration/?domain=tesla_custom.
validations:
required: true

Expand Down

0 comments on commit e531317

Please sign in to comment.