Conversation
45c7742 to
8176dfc
Compare
beeme1mr
left a comment
There was a problem hiding this comment.
How does Snap pick up the changes?
toddbaert
left a comment
There was a problem hiding this comment.
I know very little about snaps, but I certainly trust @AlexsJones to, given his associations!
Along with @beeme1mr, I'm unsure how snapcraft.io "knows" about this package given there's no publish CI or anything here. Is snapcraft.io configured to look at the yaml file in this repo periodically?
beeme1mr
left a comment
There was a problem hiding this comment.
Agreed, this looks good. I would just like to understand the process a bit.
Thanks for putting this together @AlexsJones!
Currently this is adding in the settings for publishing, the publishing itself is still manual at this point e.g. you have to be logged in and run |
Signed-off-by: Skye Gill <gill.skye95@gmail.com> Signed-off-by: Alex <alexsimonjones@gmail.com>
Signed-off-by: Alex <alexsimonjones@gmail.com>
Signed-off-by: Alex <alexsimonjones@gmail.com>
Signed-off-by: Alex <alexsimonjones@gmail.com>
Signed-off-by: Alex <alexsimonjones@gmail.com>
30934bb to
4077acc
Compare
🤖 I have created a release *beep* *boop* --- ## [0.2.7](v0.2.5...v0.2.7) (2022-12-02) ### ⚠ BREAKING CHANGES * start command flag refactor ([#222](#222)) ### Features * enable request logging via the --debug flag ([#226](#226)) ([11954b5](11954b5)) * Resurrected the STATIC flag reason. Documented the caching strategy. ([#224](#224)) ([5830592](5830592)) * snap ([#211](#211)) ([c619844](c619844)) * start command flag refactor ([#222](#222)) ([14474cc](14474cc)) ### Miscellaneous Chores * release v0.2.6 ([93cfb78](93cfb78)) * release v0.2.7 ([4a9f6df](4a9f6df)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Adding snap configuration and badge