Ignore the protocol maps, Toyota's beside Anker's
The Anker protocol maps are kept out of the tree as local copies of published artifacts; the Toyota API map is the same kind of file and joins the rule. The file itself stays on disk. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
1 parent
f8b39fa0a3
commit
143917f0bb
1 file changed
+3
-2
+3
-2
@@ -16,6 +16,7 @@ Thumbs.db
|
||||
.env
|
||||
*.env.local
|
||||
|
||||
# Local reference copies of the published Anker protocol map artifacts
|
||||
# (Modbus TCP, cloud MQTT, cloud REST API, OCPP)
|
||||
# Local reference copies of the published protocol map artifacts
|
||||
# (Anker: Modbus TCP, cloud MQTT, cloud REST API, OCPP; Toyota: cloud REST API)
|
||||
anker-*-map.html
|
||||
toyota-*-map.html
|
||||
Reference in new issue
Block a user