Sharing code on Github is a modern standard for open source development. When creating a new skill within the developer console, it is possible to import the skill directly form Github. The drawback, this creates a new git repository and the history of the Github repository is not connected.
Looking for
What I am actually looking for is the option to clone the Git repository and to create the new Alexa Skill within the own Alexa account, while keeping to the commit history connected. This may require some local configuration, maybe in .env style, those credentials that don't belong to Github.
Missing feature or missing documentation?
I was not able to figure out within a reasonable amount of time, if this is a missing feature of the Ask Toolkit or if the path to the documentation isn't paved that well.
Question
Given
Sharing code on Github is a modern standard for open source development. When creating a new skill within the developer console, it is possible to import the skill directly form Github. The drawback, this creates a new git repository and the history of the Github repository is not connected.
Looking for
What I am actually looking for is the option to clone the Git repository and to create the new Alexa Skill within the own Alexa account, while keeping to the commit history connected. This may require some local configuration, maybe in
.env
style, those credentials that don't belong to Github.Missing feature or missing documentation?
I was not able to figure out within a reasonable amount of time, if this is a missing feature of the Ask Toolkit or if the path to the documentation isn't paved that well.