/explore
|
You are here 
|
kinoshita.eti.br | ||
| | | | |
localheinz.com
|
|
| | | | | Since GitHub introduced the automatic generation of release notes, creating releases with release notes has become easier than ever. | |
| | | | |
fusectore.dev
|
|
| | | | | During one of my assignments, I worked with GitHub Actions pretty much every day. I implemented workflows, created new actions, and helped people migrate their projects from jenkins to actions. As much as I like actions and I like them a lot there are some things that caught me off guard. I have collected some of these things, both for other people to let them know, and for myself as a future reference. How well do you know actions? Can you answer all of these questions correctly? Assume that all YA... | |
| | | | |
tech.michaelaltfield.net
|
|
| | | | | How to detect malicious bidirectional unicode characters in PR commits using a GitHub Actions workflow (Defending against Trojan Source attacks) | |
| | | | |
werat.dev
|
|
| | | Benchmarks are often underestimated and don't get the same attention as tests. However "performance is a feature" and when something is not tested it might as well be just broken. If the performance is not measured/tracked regressions are inevitable. Modern tooling makes it really easy to write benchmarks. Some languages have built-in support, for example, Rust comes with cargo bench (docs) and Go has go test -bench (docs). For C++ there is google/benchmark - not as streamlined as having it built into the language infrastructure, but still definitely worth the effort. | ||
