Skip to content

Instantly share code, notes, and snippets.

View quinoescobar's full-sized avatar

J. Joaquín Escobar G. quinoescobar

  • Arte Consultores Tecnológicos
  • Tenerife
  • 09:08 (UTC +01:00)
View GitHub Profile
@quinoescobar
quinoescobar / launch.json
Created January 9, 2019 15:24
VS Code Debugger: Angular + Chronium
{
"version": "0.2.0",
"configurations": [
{
"type": "chrome",
"request": "launch",
"name": "Launch Chromium against localhost",
"url": "http://localhost:4200/#",
"webRoot": "${workspaceFolder}",
"runtimeExecutable": "/usr/bin/chromium-browser",
@quinoescobar
quinoescobar / git-aliases.md
Created February 7, 2018 10:58 — 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