git checkout master # you can avoid this line if you are in master...
git subtree split --prefix dist -b gh-pages # create a local gh-pages branch containing the splitted output folder
git push -f origin gh-pages:gh-pages # force the push of the gh-pages branch to the remote gh-pages branch at origin
git branch -D gh-pages # delete the local gh-pages because you will need it: ref
NUMBER | CODE | SERIAL | NAME | TYPE1 | TYPE2 | COLOR | ABILITY1 | ABILITY2 | ABILITY HIDDEN | GENERATION | LEGENDARY | MEGA_EVOLUTION | HEIGHT | WEIGHT | HP | ATK | DEF | SP_ATK | SP_DEF | SPD | TOTAL | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | 1 | 11 | Bulbasaur | Grass | Poison | Green | Overgrow | Chrolophyll | 1 | 0 | 0 | 0.7 | 6.9 | 45 | 49 | 49 | 65 | 65 | 45 | 318 | ||
2 | 1 | 21 | Ivysaur | Grass | Poison | Green | Overgrow | Chrolophyll | 1 | 0 | 0 | 1 | 13 | 60 | 62 | 63 | 80 | 80 | 60 | 405 | ||
3 | 1 | 31 | Venusaur | Grass | Poison | Green | Overgrow | Chrolophyll | 1 | 0 | 0 | 2 | 100 | 80 | 82 | 83 | 100 | 100 | 80 | 525 | ||
3 | 2 | 32 | Mega Venusaur | Grass | Poison | Green | Thick Fat | 1 | 0 | 1 | 2.4 | 155.5 | 80 | 100 | 123 | 122 | 120 | 80 | 625 | |||
4 | 1 | 41 | Charmander | Fire | Red | Blaze | Solar Power | 1 | 0 | 0 | 0.6 | 8.5 | 39 | 52 | 43 | 60 | 50 | 65 | 309 | |||
5 | 1 | 51 | Charmeleon | Fire | Red | Blaze | Solar Power | 1 | 0 | 0 | 1.1 | 19 | 58 | 64 | 58 | 80 | 65 | 80 | 405 | |||
6 | 1 | 61 | Charizard | Fire | Flying | Red | Blaze | Solar Power | 1 | 0 | 0 | 1.7 | 90.5 | 78 | 84 | 78 | 109 | 85 | 100 | 534 | ||
6 | 2 | 62 | Mega Charizard X | Fire | Dragon | Black | Tough Claws | 1 | 0 | 1 | 1.7 | 110.5 | 78 | 130 | 111 | 130 | 85 | 100 | 634 | |||
6 | 3 | 63 | Mega Charizard Y | Fire | Flying | Red | Drought | 1 | 0 | 1 | 1.7 | 90.5 | 78 | 104 | 78 | 159 | 115 | 100 | 634 |
Slack doesn't provide an easy way to extract custom emoji from a team. (Especially teams with thousands of custom emoji) This Gist walks you through a relatively simple approach to get your emoji out.
If you're an admin of your own team, you can get the list of emoji directly using this API: https://api.slack.com/methods/emoji.list. Once you have it, skip to Step 3
HOWEVER! This gist is intended for people who don't have admin access, nor access tokens for using that list.
Follow along...
## within current branch, squashes all commits that are ahead of master down into one | |
## useful if you merged with upstream in the middle of your commits (rebase could get very ugly if this is the case) | |
## commit any working changes on branch "mybranchname", then... | |
git checkout master | |
git checkout -b mybranchname_temp | |
git merge --squash mybranchname | |
git commit -am "Message describing all squashed commits" | |
git branch -m mybranchname mybranchname_unsquashed | |
git branch -m mybranchname |
#Mobile Device Detection via User Agent RegEx
Yes, it is nearly 2012 and this exercise has been done to death in every imaginable language. For my own purposes I needed to get the majority of non-desktop devices on to a trimmed down, mobile optimized version of a site. I decided to try and chase down an up-to-date RegEx of the simplest thing that could possibly work.
I arrived at my current solution after analyzing 12 months of traffic over 30+ US based entertainment properties (5.8M+ visitors) from Jan - Dec 2011.
The numbers solidified my thoughts on the irrelevancy of including browsers/OSes such as Nokia, Samsung, Maemo, Symbian, Ipaq, Avant, Zino, Bolt, Iris, etc. The brass tacks of the matter is that you certainly could support these obscure beasts, but are you really going to test your site on them? Heck, could you even find one?! Unless the folks that pay you are die hard Treo users my guess is "No".
Interestingly enough my research shows that /Mobile/ is more efficient than **/iP(