/explore
|
You are here 
|
fusectore.dev | ||
| | | | |
wittchen.io
|
|
| | | | | Recently GitHub introduced really interesting feature to their service called Actions. Actions can be used for automating various tasks related to the repositories like CI, CD, testing, deployment and whatnot. The general concept is as follows: We can create so called action, which can be based on a JavaScript project or a Docker container. We can also use existing actions in the Marketplace. Next, we can create workflow in the yml file, where we define our workflow. Workflow can consist of on a job with many steps using different actions. We can also define multiple jobs, where one depends on another. Workflows can be triggered in many ways. E.g. by push, pull request, creating issue, publishing release, scheduled event or external event. | |
| | | | |
www.blog.pythonlibrary.org
|
|
| | | | | When you are working on your personal or work projects in Python, you usually want to have a way to enforce code standards. You can use tools like Flake8, | |
| | | | |
www.architect.io
|
|
| | | | | Learn how to automate the steps to build, test, and deploy your code using GitHub Actions. | |
| | | | |
mrcat.au
|
|
| | | I've started learning Zig, a new programming language in the same problem space as C, and it has some features I really like. While it's not memory-safe in the Rust way, it has a lot of compile time and runtime checks to prevent common footguns. It has packed structs and variable-width integers to allow for easy parsing of bitpacked binary formats. Its comptime metaprogramming capabilities are spectacular. And it even interoperates seamlessly with C! | ||
