| Function | Shortcut |
|---|---|
| Fullscreen | ⌘+ Enter |
| Previous Tab | ⌘+ Left Arrow |
| Next Tab | ⌘+ Right Arrow |
| Go to Tab | ⌘ + Number |
| Go to Window | ⌘ + Option + Number |
| Go to Split Pane by Direction | ⌘ + Option + Arrow |
Rhe JackHo327
JackHo327
/ iterm2.md
Created
April 11, 2018 05:21
— forked from squarism/iterm2.md
iterm2 cheatsheet
JackHo327
/ git-feature-workflow.md
Created
March 15, 2018 20:30
— forked from blackfalcon/git-feature-workflow.md
Git basics - a general workflow
There are many Git workflows out there, I heavily suggest also reading the atlassian.com [Git Workflow][article] article as there is more detail then presented here.
The two prevailing workflows are [Gitflow][gitflow] and [feature branches][feature]. IMHO, being more of a subscriber to continuous integration, I feel that the feature branch workflow is better suited.
When using Bash in the command line, it leaves a bit to be desired when it comes to awareness of state. I would suggest following these instructions on [setting up GIT Bash autocompletion][git-auto].
When working with a centralized workflow the concepts are simple, master represented the official history and is always deployable. With each now scope of work, aka feature, the developer is to create a new branch. For clarity, make sure to use descriptive names like transaction-fail-message or github-oauth for your branches.