Correct usage of snapcraft.yaml

Mark Shuttleworth mark at
Thu Jan 5 13:48:19 UTC 2017

On 05/01/17 15:39, gareth.france at wrote:
> Once again please do forgive my lack of knowledge. Having managed to
> successfully release a snap I am now wondering what the correct thing
> to do is regarding github. My code is there for anyone to obtain, so
> should the snapcraft.yaml be included or is that something one would
> normally keep to themselves? 

Would encourage you to have the snapcraft.yaml in the git tree; it makes
it easier for people to contribute to that. Also, if the code is
evolving, would encourage you to setup Travis or other CI integration so
that you get an automatic edge release for (edgy) users :)


More information about the Snapcraft mailing list