Juan Alvarez nebiros
| { | |
| "apiVersion": "dashboard.grafana.app/v2beta1", | |
| "kind": "Dashboard", | |
| "metadata": { | |
| "name": "claude-code-metrics", | |
| "generation": 12, | |
| "creationTimestamp": "2025-12-10T13:33:56Z", | |
| "labels": {}, | |
| "annotations": {} | |
| }, |
I get asked pretty regularly what my opinion is on merge commits vs rebasing vs squashing. I've typed up this response so many times that I've decided to just put it in a gist so I can reference it whenever it comes up again.
I use merge, squash, rebase all situationally. I believe they all have their merits but their usage depends on the context. I think anyone who says any particular strategy is the right answer 100% of the time is wrong, but I think there is considerable acceptable leeway in when you use each. What follows is my personal and professional opinion:
| // ==UserScript== | |
| // @name Medium Paywall Bypass | |
| // @namespace Violentmonkey Scripts | |
| // @run-at document-start | |
| // @match *://*.medium.com/* | |
| // @match *://medium.com/* | |
| // @match *://*/* | |
| // @grant none | |
| // @version 3.0 | |
| // @inject-into content |
If someone asked me the question "what layout should I use for my Go code repository?", I'd start by asking back "what are you building: an executable, or a library?"
Create a directory named however you want your final executable to be called (e.g. "mycommand"), change into that directory, and create the following files:
| # Using these pry gems -- copy to your Gemfile | |
| # group :development, :test do | |
| # gem 'awesome_print' # pretty print ruby objects | |
| # gem 'pry' # Console with powerful introspection capabilities | |
| # # pick either: | |
| # # using byebug, but has issues with Zeitwerk | |
| # gem 'pry-byebug' # Integrates pry with byebug | |
| # | |
| # # using default ruby debuggger | |
| # gem 'pry-stack_explorer' |
| # Referenced videos: | |
| # - Argo CD - Applying GitOps Principles To Manage Production Environment In Kubernetes: https://youtu.be/vpWQeoaiRM4 | |
| # - kind - How to run local multi-node Kubernetes clusters: https://youtu.be/C0v5gJSWuSo | |
| # - GitHub CLI - How to manage repositories more efficiently: https://youtu.be/BII6ZY2Rnlc | |
| # - Argo Workflows and Pipelines - CI/CD, Machine Learning, and Other Kubernetes Workflows: https://youtu.be/UMaivwrAyTA | |
| # - Running Jenkins In Kubernetes - Tutorial And Review: https://youtu.be/2Kc3fUJANAc | |
| # - Github Actions Review And Tutorial: https://youtu.be/eZcAvTb0rbA | |
| # - Tekton - Kubernetes Cloud-Native CI/CD Pipelines And Workflows: https://youtu.be/7mvrpxz_BfE | |
| # - Environments Based On Pull Requests (PRs): Using Argo CD To Apply GitOps Principles On Previews: https://youtu.be/cpAaI8p4R60 | |
| # - How To Apply GitOps To Everything - Combining Argo CD And Crossplane: https://youtu.be/yrj4lmScKHQ |
08/16/17 by Sergey Grebenshchikov
This is a quick tutorial on how to test code using the GoMock mocking library and the standard library testing package testing.
GoMock is a mock framework for Go. It enjoys a somewhat official status as part of the github.com/golang organization, integrates well with the built-in testing package, and provides a flexible expectation API.