Explore >> Select a destination
|
You are here 
|
codeinthehole.com | ||
| | | | |
popey.com
|
|
| | | | | This is a bit of a dayjob post, but as I maintain a bunch of snaps in my own time, I figured its not out of place here. Typically when I (or indeed any developer) uses snapcraft to build a snap, a snapcraft.yaml drives the process. Ill integrate some kind of CI or build system, and start publishing to the Snap Store. Usually, once created, the yaml doesnt need much in the way of changes. | |
| | | | |
www.aleksandrhovhannisyan.com
|
|
| | | | | It can be tempting to lump unrelated code changes into a single commit, but this makes it difficult to debug and time travel in Git. Prefer to write atomic commits that have a single responsibility. | |
| | | | |
simonwillison.net
|
|
| | | | | For the last few years I've been trying to center my work around creating what I consider to be the Perfect Commit. This is a single commit that contains all ... | |
| | | | |
www.redapt.com
|
|
| | | Maintaining your AI is a critical part of ensuring optimal future performance. Discover the right strategies and tactics to keep your AI relevant and accurate. | ||
