If you have committed junk but not pushed
git reset --soft HEAD~1
| In terminal run | |
| ulimit -n 8192 |
If you have committed junk but not pushed
git reset --soft HEAD~1
| // Use Gists to store code you would like to remember later on | |
| console.log(window); // log the "window" object to the console |
| git remote add upstream THE_SOURCE_REPO | |
| git remote add YOUR_USER_NAME YOUR_FORK | |
| git remote set-url origin THE_SOURCE_REPO | |
| git remote set-url origin --push YOUR_FORK | |
| git config --global push.default current |
##How to start as a Front-End Developer
I've been asked this question many times by friends/colleagues and never had the chance to answer it properly.
I believe it's not about how many things you need to know more than it's a process you should flow. also it's not all about learning you should practice skills you gained and sharpen them often.
So, I curated here what could work as a plan/resources for you to use:
It's about semantics here you should know how you can fully describe structure of data you are displaying and when to use different tags to describe what. This important for maintainability/performance of your code and also for search engine and screen readers.
| git branch --merged | grep -v "\*" | grep -v master | grep -v dev | xargs -n 1 git branch -d |
| "auto_complete_triggers": [ | |
| { | |
| "characters": ".@", | |
| "selector": "source.coffee, source.litcoffee, source.coffee.md" | |
| } | |
| ] |
| git branch -m old_branch new_branch # Rename branch locally | |
| git push origin :old_branch # Delete the old branch | |
| git push --set-upstream origin new_branch # Push the new branch, set local branch to track the new remote |