raorao

Any top-level comment on pull request ought be tagged with one of four emojis:

• ❓ for a non-blocking comment that asks for clarification. The pull request author must answer the question before the pull request is merged, but does not have to wait for the comment author to re-review before merging.

• 🎨 for a non-blocking comment that proposes a refactor or cleanup. The pull request author does not have to address the comment for the pull request to merge.

• ⚠️ for a blocking comment that must be addressed before the pull request can merge. The comment's author should leave a Request Changes review, and is responsible for re-reviewing once the pull request author has addressed the issue.

• 😻 for a comment that compliments the author for their work.

ericclemmons

Using <details> in GitHub

Suppose you're opening an issue and there's a lot noisey logs that may be useful.

Rather than wrecking readability, wrap it in a <details> tag!

<details>
 Summary Goes Here

ndelage

Unix Command Line Fu

Basics

tab completion

Nearly all shells have support for tab completion. At a minimum for completing file & directory names, though some even tab-complete based on which commands you're running. Some examples:

$ ls [TAB]
Gemfile app/ connectors.rb public/