Skip to content

Instantly share code, notes, and snippets.

View helderberto's full-sized avatar

Helder Burato Berto helderberto

View GitHub Profile
@helderberto
helderberto / git-branching-model.md
Last active November 11, 2017 01:07 — forked from digitaljhelms/gist:4287848
Git/GitHub branching standards & conventions

Branching

Quick Legend

Description, Instructions, Notes
Instance Branch
@helderberto
helderberto / docker_kill.sh
Created March 1, 2018 22:21 — forked from evanscottgray/docker_kill.sh
kill all docker containers at once...
docker ps | awk {' print $1 '} | tail -n+2 > tmp.txt; for line in $(cat tmp.txt); do docker kill $line; done; rm tmp.txt
@helderberto
helderberto / Remove all git tags
Created March 18, 2018 22:03 — forked from okunishinishi/Remove all git tags
Delete all git remote tags
#Delete local tags.
git tag -l | xargs git tag -d
#Fetch remote tags.
git fetch
#Delete remote tags.
git tag -l | xargs -n 1 git push --delete origin
#Delete local tasg.
git tag -l | xargs git tag -d
@helderberto
helderberto / git-aliases.md
Created March 20, 2018 23:24 — forked from mwhite/git-aliases.md
The Ultimate Git Alias Setup

The Ultimate Git Alias Setup

If you use git on the command-line, you'll eventually find yourself wanting aliases for your most commonly-used commands. It's incredibly useful to be able to explore your repos with only a few keystrokes that eventually get hardcoded into muscle memory.

Some people don't add aliases because they don't want to have to adjust to not having them on a remote server. Personally, I find that having aliases doesn't mean I that forget the underlying commands, and aliases provide such a massive improvement to my workflow that it would be crazy not to have them.

The simplest way to add an alias for a specific git command is to use a standard bash alias.

# .bashrc
@helderberto
helderberto / README-Template.md
Created June 1, 2018 19:02 — forked from PurpleBooth/README-Template.md
A template to make good README.md

Project Title

One Paragraph of project description goes here

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

Prerequisites

Contributing

When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.

Please note we have a code of conduct, please follow it in all your interactions with the project.

Pull Request Process

  1. Ensure any install or build dependencies are removed before the end of the layer when doing a
@helderberto
helderberto / settings.json
Last active August 28, 2018 15:48
VS Code - User Settings
// Place your settings in this file to overwrite the default settings
{
"editor.tabSize": 2,
"editor.detectIndentation": false,
"editor.insertSpaces": true,
"editor.fontSize": 12,
"workbench.welcome.enabled": false,
"editor.renderWhitespace": "all",
"diffEditor.ignoreTrimWhitespace": false,
"window.zoomLevel": 1,
@helderberto
helderberto / estados-cidades.json
Created September 13, 2018 19:19 — forked from letanure/estados-cidades.json
JSON estados cidades
{
"estados": [
{
"sigla": "AC",
"nome": "Acre",
"cidades": [
"Acrelândia",
"Assis Brasil",
"Brasiléia",
"Bujari",
@helderberto
helderberto / npm-init.md
Last active January 14, 2019 00:13
NPM Default Config

Initial Configs

npm set init-author-name "Your name"
npm set init-author-email "your@email.com"
npm set init-author-url "https://yoururl.com"
npm set init-license "MIT" <choose your prefered license>

Reference

@helderberto
helderberto / git-cheat-sheet.md
Last active March 18, 2019 20:52
Git Cheat Sheet

CONFIGURATION

See all local configs:

git config --list

Get username or email:

git config user.name