Various configuration files for my working environment
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#! /bin/bash | |
set -eu | |
BRANCH='' | |
ORG='okp4' | |
USER=ad2ien | |
REPOS=$(gh repo list ${ORG} --source --limit 150 --no-archived --json name --template '{{range .}}{{ .name }} {{end}}') | |
echo $REPOS |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/bash -e | |
REPO_DIR="$(realpath ${1:-.})" | |
for repo in $(find "$REPO_DIR" -mindepth 1 -maxdepth 1 -type d) | |
do | |
if [ ! -d "$repo/.git" ] | |
then | |
echo "Skipping $repo. Not a git repo" | |
continue |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# This code is licensed under the terms of the MIT license https://opensource.org/license/mit | |
# Copyright (c) 2021 Marat Reymers | |
## Golden config for golangci-lint v1.59.1 | |
# | |
# This is the best config for golangci-lint based on my experience and opinion. | |
# It is very strict, but not extremely strict. | |
# Feel free to adapt and change it for your needs. | |
run: |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
import { Comonad2C } from 'fp-ts/lib/Comonad'; | |
import { pipe } from 'fp-ts/lib/function'; | |
import { FunctionN } from 'fp-ts/lib/function'; | |
import { Monoid } from 'fp-ts/lib/Monoid'; | |
import { NonEmptyArray } from 'fp-ts/lib/NonEmptyArray'; | |
import { pipeable } from 'fp-ts/lib/pipeable'; | |
/** | |
* OOP style builder pattern but in FP | |
* References: |
Tutorial and tips for GitHub Actions workflows
(This is a fork of Michael's original gist with some editing of the unions + records sections.)
Each of these examples assume the usage of --strict
mode in Typescript
Can be implemented using “Custom Types”
See how a minor change to your commit message style can make a difference.
Tip
Have a look at git-conventional-commits , a CLI util to ensure these conventions, determine version and generate changelogs
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
term | description | value/example | |
---|---|---|---|
organization | The name of the organization | google/facebook etc. | |
service | Name of the service | myApp | |
resource | Name of the resource being monitored by the service. It could also simply be a method name in the application | kafka/method1/database | |
entity | Name of the attribute being operated on. It's context is defined by the resource | message/schema | |
metricType | Type of metric for easy identification | gauge/meter/timer etc. | |
operation | Defines the type of metric to use | create/update/delete/count/read | |
status | Status of the operation | success/failed/delay/abort |
NewerOlder