Implement complete tesselinclude detect spec. Closes gh-638 #639
Conversation
|
Awesome update! 👍 LGTM |
lib/tessel/deploy.js
Outdated
| ${assets.join('\n')} | ||
| If you need to deploy them to your Tessel 2, you must create a .tesselinclude |
There was a problem hiding this comment.
should this be "create" a .tesselinclude or something else to reflect that they probably have one due to t2 init?
There was a problem hiding this comment.
If the project wasn't started with t2 init, they will have to create the file. We could also say "type t2 init", but what if they did and purposely deleted the .tesselinclude file, thinking that they didn't need to use it? It might seem strange to say "run t2 init" to someone that already did that.
|
Made a PR to the start page to reflect the changes: tessel/t2-start#88 |
Signed-off-by: Rick Waldron <[email protected]>
| file that lists the file and directory assets for your application. This can be | ||
| created manually or by typing 't2 init'. | ||
| For more information, visit: https://tessel.io/docs/cli#starting-projects |
There was a problem hiding this comment.
@Frijol thanks for review—I think this is much better, but let me know!
|
looks good to me! |
|
@Frijol thanks for the review and follow up! |
…ssel#639) Signed-off-by: Rick Waldron <[email protected]>
@HipsterBrown review?
Signed-off-by: Rick Waldron [email protected]