hcastro

---
description: >
  Git Commit Assistant rule to enforce clean,
  structured, and traceable commit workflows. This rule should be applied
  whenever a developer attempts to stage or commit changes. It ensures that:
  - Commits are grouped logically and use conventional commit messages tied to Jira tickets.
  - Feature branches are created from `development` with proper naming conventions.
  - No direct work is allowed on `master`.
  - Sensitive or excluded files (e.g., .env, secrets) are never accidentally committed.
  This rule improves collaboration, auditability, and consistency across the codebase,

gzomer

(function () {
    Error;
    console.log('aca')
    function e(t, n, o) {
        const r = o();
        return t > 0 ? r.catch((r) => new Promise((e, t) => setTimeout(e, n)).then((r) => e(t - 1, n, o))) : r;
    }
    var t;
    !(function (e) {
        function t() {

BigNerd

View: Pods(<namespace>)[number of pods listed]

NAME      pod name
READY     number of pods in ready state / number of pods to be in ready state
RESTARTS  number of times the pod has been restarted so far
STATUS    state of the pod life cycle, such as Running | ... | Completed
CPU       current CPU usage, unit is milli-vCPU
MEM       current main memory usage, unit is MiB
%CPU/R    current CPU usage as a percentage of what has been requested by the pod
%MEM/R    current main memory usage as a percentage of what has been requested by the pod

ChristopherA

Brew Bundle Brewfile Tips

Copyright & License

Unless otherwise noted (either in this file or in a file's copyright section) the contents of this gist are Copyright ©️2020 by Christopher Allen, and are shared under spdx:Creative Commons Attribution Share Alike 4.0 International (CC-BY-SA-4.) open-source license.

Sponsor

If you more tips and advice like these, you can become a monthly patron on my GitHub Sponsor Page for as little as $5 a month; and your contributions will be multipled, as GitHub is matching the first $5,000! This gist is all about Homebrew, so if you like it you can support it by donating to them or becoming one of their Github Sponsors.

OliverJAsh

Option vs non-Option

	Option<T>	non-Option (T | undefined)
accessing property	userOption.map(user => user.age)	userNullish?.age
calling a method	userOption.map(user => user.fn())	userNullish?.fn()
providing fallback	ageOption.getOrElse(0)	ageNullish ?? 0
filter	ageOption.filter(checkIsOddNumber)	`ageNull

jfcherng

This gist will no longer be updated as the changelog will be on the official website.

• Sublime Text/Merge Official Discord chat server: https://discord.gg/D43Pecu
• Sublime Text/Merge 中文 Telegram 交流群組： https://t.me/sublime_tw

Converted via https://domchristie.github.io/turndown

About Sublime Text 4

mhulse

#!/usr/bin/env bash

SOURCE="${BASH_SOURCE[0]}"
while [ -h "$SOURCE" ]; do # resolve $SOURCE until the file is no longer a symlink
  DIR="$(cd -P "$(dirname "$SOURCE")" >/dev/null 2>&1 && pwd)"
  SOURCE="$(readlink "$SOURCE")"
  [[ $SOURCE != /* ]] && SOURCE="$DIR/$SOURCE" # if $SOURCE was a relative symlink, we need to resolve it relative to the path where the symlink file was located
done
DOTFIZZLES="$(cd -P "$( dirname "$SOURCE" )" >/dev/null 2>&1 && pwd)"
export DOTFIZZLES

eanakashima

slides

1. Talk about birds for five minutes

• Hawks vs. Falcons
• Observability vs. Metrics (Cindy Sridharan)

2. Data models

• Events vs. Structured Logs (Ben Hartshorne, Honeycomb.io)

gregopet

jooq.fetchOne("select * from film limit 1");

// type safety for fields
jooq.fetchOne("select * from film limit 1").get(FILM.TITLE);
jooq.fetchOne("select title || ' ' || description from film limit 1").get(0, String.class);

// parameters
jooq
  .fetchOne("select title || ' ' || description from film where title like ? limit 1", "DINOSAUR%")
  .get(0, String.class);

Jabarabo

Awesome Piracy

A curated list of arrrrrrrrr!

Contents

• Preamble
• Mirrors
• How to use this list
• Emoji
• Background Information