Skip to content

Instantly share code, notes, and snippets.

View mselmany's full-sized avatar

numano mselmany

View GitHub Profile
#!/bin/bash
# Searchs $FILE's $TEXT changes in all branches
# Author: Yunus Oksuz <yunusoksuz@gmail.com>
# track all remote branches
git branch -a | grep -v HEAD | perl -ne 'chomp($_); s|^\*?\s*||; if (m|(.+)/(.+)| && not $d{$2}) {print qq(git branch --track $2 $1/$2\n)} else {$d{$_}=1}' | csh -xfs
TEXT="1\\.8\\.76"
FILE="build.gradle"
@mselmany
mselmany / cloudSettings
Last active April 23, 2018 10:42
Visual Studio Code Settings Sync Gist
{"lastUpload":"2018-04-23T10:42:36.113Z","extensionVersion":"v2.9.0"}
@mselmany
mselmany / cloudSettings
Last active May 4, 2017 20:46
Visual Studio Code Settings Sync Gist
{"lastUpload":"2017-05-04T20:46:55.042Z","extensionVersion":"v2.7.0"}
@mselmany
mselmany / cloudSettings
Last active May 4, 2017 16:53
Visual Studio Code Settings Sync Gist
{"lastUpload":"2017-05-04T16:53:20.797Z","extensionVersion":"v2.7.0"}
@mselmany
mselmany / env-examples.md
Created November 27, 2016 21:59 — forked from ericelliott/env-examples.md
env-examples

Most configuration really isn't about the app -- it's about where the app runs, what keys it needs to communicate with third party API's, the db password and username, etc... They're just deployment details -- and there are lots of tools to help manage environment variables -- not the least handy being a simple .env file with all your settings. Simply source the appropriate env before you launch the app in the given env (you could make it part of a launch script, for instance).

env files look like this:

SOMEVAR="somevalue"
ANOTHERVAR="anothervalue"

To source it:

$ source dev.env # or staging.env, or production.env, depending on where you're deploying to

@mselmany
mselmany / trello-css-guide.md
Created March 10, 2016 23:29 — forked from bobbygrace/trello-css-guide.md
Trello CSS Guide

Hello, visitors! If you want an updated version of this styleguide in repo form with tons of real-life examples… check out Trellisheets! https://github.com/trello/trellisheets


Trello CSS Guide

“I perfectly understand our CSS. I never have any issues with cascading rules. I never have to use !important or inline styles. Even though somebody else wrote this bit of CSS, I know exactly how it works and how to extend it. Fixes are easy! I have a hard time breaking our CSS. I know exactly where to put new CSS. We use all of our CSS and it’s pretty small overall. When I delete a template, I know the exact corresponding CSS file and I can delete it all at once. Nothing gets left behind.”

You often hear updog saying stuff like this. Who’s updog? Not much, who is up with you?

{"countries":[{"name":"T\u00fcrkiye","url":"turkiye"},{"name":"ABD","url":"abd"},{"name":"Afganistan","url":"afganistan"},{"name":"Almanya","url":"almanya"},{"name":"Andorra","url":"andorra"},{"name":"Angola","url":"angola"},{"name":"Anguilla","url":"anguilla"},{"name":"Antigua ve Barbuda","url":"antigua-ve-barbuda"},{"name":"Arjantin","url":"arjantin"},{"name":"Arnavutluk","url":"arnavutluk"},{"name":"Aruba","url":"aruba"},{"name":"Avustralya","url":"avustralya"},{"name":"Avusturya","url":"avusturya"},{"name":"Azerbaycan","url":"azerbaycan"},{"name":"Bahamalar","url":"bahamalar"},{"name":"Bahreyn","url":"bahreyn"},{"name":"Banglades","url":"banglades"},{"name":"Barbados","url":"barbados"},{"name":"Belarus","url":"belarus"},{"name":"Belcika","url":"belcika"},{"name":"Belize","url":"belize"},{"name":"Benin","url":"benin"},{"name":"Bermuda","url":"bermuda"},{"name":"Birlesik Arap Emirligi","url":"birlesik-arap-emirligi"},{"name":"Bolivya","url":"bolivya"},{"name":"Bosna Hersek","url":"bosna-hersek"},{"name":"Bo