Skip to content

Instantly share code, notes, and snippets.

View fakenickels's full-sized avatar
hello this is a mic test, are you listening

Gabriel Rubens Abreu fakenickels

hello this is a mic test, are you listening
View GitHub Profile
View deploy.yml
name: deploy
branches: [ master ]
tags: [ v* ]
runs-on: macos-latest
fakenickels / metro.config.js
Last active December 22, 2019 04:54 — forked from sibelius/metro.config.js
metro config to work with yarn workspaces
View metro.config.js
const path = require('path');
const getWorkspaces = require('get-yarn-workspaces');
const blacklist = require('metro-config/src/defaults/blacklist');
const workspaces = getWorkspaces(__dirname);
// Blacklists any react-native that doesn't come from packages/app
const blacklistRE = blacklist([ /(?<!packages\/app\/)node_modules\/react-native\/.*/g])
fakenickels /
Created October 21, 2017 18:43 — forked from manasthakur/
Using git submodules to version-control Vim plugins

Using git-submodules to version-control Vim plugins

If you work across many computers (and even otherwise!), it's a good idea to keep a copy of your setup on the cloud, preferably in a git repository, and clone it on another machine when you need. Thus, you should keep the .vim directory along with your .vimrc version-controlled.

But when you have plugins installed inside .vim/bundle (if you use pathogen), or inside .vim/pack (if you use Vim 8's packages), keeping a copy where you want to be able to update the plugins (individual git repositories), as well as your vim-configuration as a whole, requires you to use git submodules.

Creating the repository

Initialize a git repository inside your .vim directory, add everything (including the vimrc), commit and push to a GitHub/BitBucket/GitLab repository:

cd ~/.vim
View estados-cidades.json
"estados": [
"sigla": "AC",
"nome": "Acre",
"cidades": [
"Assis Brasil",