Skip to content

Instantly share code, notes, and snippets.

View jacilynh's full-sized avatar
:octocat:
Be here now.

Jaci Hayden jacilynh

:octocat:
Be here now.
17 followers · 25 following
View GitHub Profile
@jacilynh
jacilynh / gist:f6f8cf6474d5d14ae8dd723a46c4dc7f
Created October 14, 2018 16:20 — forked from tobyhede/gist:3179978
Ruby/Rails date format cheat sheet
From http://linux.die.net/man/3/strftime
%a - The abbreviated weekday name (``Sun'')
%A - The full weekday name (``Sunday'')
%b - The abbreviated month name (``Jan'')
%B - The full month name (``January'')
%c - The preferred local date and time representation
%d - Day of the month (01..31)
%e - Day of the month without leading 0 (1..31)
%g - Year in YY (00-99)
@jacilynh
jacilynh / Keyboard Shortcuts.md
Created October 10, 2017 00:47 — forked from deanrather/Keyboard Shortcuts.md
Keyboard Shortcuts (Sublime, Gmail, Chrome, Bash)

Sublime Text

ctrl+shift          Search for command
    reindent        Reindent Selection
    sort            Sort Lines
    space           Convert indentation to spaces
ctrl+p              Jump to file ( `:<n>` jump to line)
ctrl+;              Jump to keyword in file
ctrl+k,b            Hide/show Sidebar

alt+shift+ Split window into views

@jacilynh
jacilynh / git-feature-workflow.md
Created October 8, 2017 00:24 — 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].

Basic branching

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.