Hello, when I push my skill to public GitHub, should I be adding the .ask/config and skill.json to gitignore?
Follow on question. Assuming the answer above is YES, when someone wants to ask new --url <my git repo url>, they obviously need to create their own skill.json and .ask/config files..
Is there a better way to share and collaborate skills using GitHub?
Hey @ajhstn
Thanks for using ask-cli and this is a really good question.
First I suggest you to keep but empty the .ask/config file since right now CLI cannot deploy without this config file... But a valid empty (example) one will make sure CLI deploys correctly.
Second for the skill.json, since it contains important skill metadata, and not very developer-specific except Lambda ARNs, you need to contain this file. Since CLI supports Lambda functionName for the "uri" fields in "manifest.apis.{skillType}", your template's users will just create the Lambda with that name if you use empty config file, which is good for users to know what the Lambda is used for.
Overall, you can take reference from https://github.com/alexa/skill-sample-nodejs-hello-world as an example and this is our standard for skill project.
Hope it helps,
Ron
1 Person is following this question.
