robmiller

#
# Working with branches
#

# Get the current branch name (not so useful in itself, but used in
# other aliases)
branch-name = "!git rev-parse --abbrev-ref HEAD"
# Push the current branch to the remote "origin", and set it to track
# the upstream branch
publish = "!git push -u origin $(git branch-name)"

tholman

cd ~/Library/Application\ Support/Google/Chrome/Default/User\ StyleSheets
echo 'html {  -webkit-animation: adjustHue 20s infinite !important; }  @-webkit-keyframes adjustHue { 50% { -webkit-filter: hue-rotate(360deg); }}' >> Custom.css

codeincontext

input_file = 'input.jpg'
output_file = 'output.jpg'

def mutate(line)
  line[rand(line.length-1)] = "0"
end

File.open(input_file,'r') do |input|
  File.open(output_file,'w') do |output|
    while line = input.gets

jfromaniello

  function onlyStatic (middleware) {
    return function (req, res, next) {
      var match = /(\.css|\.eot|\.gif|\.html|\.js|\.png|\.svg|\.ttf|\.woff|\.jpg)($|\?.*$)/ig.exec(req.originalUrl);
      if (!match) return next();
      middleware(req, res, next);
    };
  }
  
  //usage
  this.use(onlyStatic(express.static(__dirname  + "/public")));

remy

Project structure

Example project directory, the root folders are pretty consistent, the sub directories (on lib, etc) are just examples of what might be in there.

.
├── lib
│   ├── db
│   ├── handlers
│   └── routes

lukas-h

Markdown License badges

Collection of License badges for your Project's README file.
This list includes the most common open source and open data licenses.
Easily copy and paste the code under the badges into your Markdown files.

Notes

• The badges do not fully replace the license informations for your projects, they are only emblems for the README, that the user can see the License at first glance.

Translations: (No guarantee that the translations are up-to-date)

• 🇫🇷 Cette liste en français

mirisuzanne

Cascade Layers, a Proposal

A syntax proposal for Cascade Layers #4470. This does not include full discussion of the Cascade Layer purpose and use-cases, which can be found in the various linked issues, but attempts to answer many of the outstanding questions about how we might implement a layering feature.

Collaborators:

• Elika Etemad
• Florian Rivoal
• Miriam Suzanne
• Tab Atkins Jr.