Skip to content

Instantly share code, notes, and snippets.

View arnaldotecadm's full-sized avatar
🎯
Focusing

Arnaldo Cícero Bezerra arnaldotecadm

🎯
Focusing
713 followers · 1.1k following
View GitHub Profile
@arnaldotecadm
arnaldotecadm / git_change_commit_alias
Created November 18, 2022 10:10 — forked from auxiliary/git_change_commit_alias
Git change commit alias
[alias]
change-commits = "!f() { VAR1=$1; VAR='$'$1; OLD=$2; NEW=$3; echo \"Are you sure for replace $VAR $OLD => $NEW ?(Y/N)\";read OK;if [ \"$OK\" = 'Y' ] ; then shift 3; git filter-branch --env-filter \"if [ \\\"${VAR}\\\" = '$OLD' ]; then export $VAR1='$NEW';echo 'to $NEW'; fi\" $@; fi;}; f "
# Usage:
# git change-commits GIT_AUTHOR_EMAIL "OLD EMAIL" "NEW EMAIL"
# git push --force --tags origin 'refs/heads/*'
@arnaldotecadm
arnaldotecadm / clean_code.md
Created October 27, 2021 12:05 — forked from wojteklu/clean_code.md
Summary of 'Clean code' by Robert C. Martin

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

General rules

  1. Follow standard conventions.
  2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
  3. Boy scout rule. Leave the campground cleaner than you found it.
  4. Always find root cause. Always look for the root cause of a problem.

Design rules