See how a minor change to your commit message style can make a difference.
Tip
Take a look at git-conventional-commits , a CLI util to ensure these conventions, determine version and generate changelogs
#!/bin/sh | |
STAGED_FILES=$(git diff-index HEAD --name-only --cached) | |
if [[ -z $STAGED_FILES ]] | |
then | |
exit # no staged files, no need to run rubocop | |
fi | |
# Checks if any staged files have unstaged changes | |
# otherwise rubocop isn't running on what is actually |
# Basic key operators to query the JSON objects : | |
# #> : Get the JSON object at that path (if you need to do something fancy) | |
# -> : Get the JSON object at that path (if you don't) | |
# ->> : Get the JSON object at that path as text | |
# {obj, n} : Get the nth item in that object | |
# https://www.postgresql.org/docs/9.4/functions-json.html#FUNCTIONS-JSONB-OP-TABLE | |
# Date | |
# date before today |
# frozen_string_literal: true | |
require 'platform-api' | |
# Adapted from GitLab | |
# | |
# Docs: https://docs.gitlab.com/ee/administration/operations/sidekiq_memory_killer.html | |
# Source: https://gitlab.com/gitlab-org/gitlab-foss/-/blob/master/lib/gitlab/sidekiq_daemon/memory_killer.rb | |
class Sidekiq::Middleware::MemoryKiller | |
# Default the RSS limit to 0, meaning the MemoryKiller is disabled (kilobytes) |
release: bin/release | |
web: ... | |
worker: ... |
See how a minor change to your commit message style can make a difference.
Tip
Take a look at git-conventional-commits , a CLI util to ensure these conventions, determine version and generate changelogs
Located in alphabetical order (not prefer)
C
ab
), also designed as a more modern replacement, written in C
golang
)