Merovex

export default function parseToMarkdown(chunk) {
  let children = !chunk.type
    ? chunk.text
    : chunk.children.map(c => parseToMarkdown({ ...c, parentType: chunk.type })).join('');

  if (children === '') return;

  // formatting
  if (chunk.bold) {
    children = `**${children.trim()}** `;

Merovex

-- Converts "* * *" Horizontal Rule to a "#" separator in Word DOCX
local hashrule = [[<w:p>
  <w:pPr>
    <w:pStyle w:val="HorizontalRule"/>
      <w:ind w:firstLine="0"/>
      <w:jc w:val="center"/>
  </w:pPr>
  <w:r>
    <w:t>#</w:t>
  </w:r>

Merovex

@function pow($base, $exponents) {
  $raised: 1;
  @for $i from 1 through $exponents {
    $raised: $raised * $base;
  }
  @return $raised;
}
@function luma($color){
  // Thanks voxpelli for a very concise implementation of luminance measure in sass
  // Adapted from: https://gist.github.com/voxpelli/6304812

Merovex

Git Commit Guidelines

We have very precise rules over how our git commit messages can be formatted. This leads to more readable messages that are easy to follow when looking through the project history. But also, we use the git commit messages to generate the AngularJS change log.

Commit Message Format

Each commit message consists of a header, a body and a footer. The header has a special format that includes a type, a scope and a subject:

Merovex

PATH=$PATH:/usr/local/bin:/usr/local/sbin
#!/bin/bash
gitbranch=`git rev-parse --abbrev-ref HEAD`
if [ $gitbranch = "master" ]; then
	date=`date +%m/%d/%Y`
	datetime=`date +%r`
	gitwa=`git diff HEAD^ HEAD --word-diff=porcelain | grep -e "^+[^+]" | wc -w`
	gitwd=`git diff HEAD^ HEAD --word-diff=porcelain | grep -e "^-[^-]" | wc -w`
	commit=`git log -1 --pretty=%B`
	cnt=`expr $gitwa - $gitwd`

Merovex

version: 2
jobs:
    build:
        docker:
            - image: paperist/alpine-texlive-ja
        steps:
            - run:
                name: Installing dependancies
                command: |
                    apk add --update git patch curl

Merovex

#!/bin/ruby

File.read("/PATH-TO/.auto-commit").split("\n").each do |dir|
  
  Dir.chdir(dir)
  next if `find . -newer .last-mod`.split("\n").empty? # No change to file system
  puts "### #{Time.new.strftime("%Y-%m-%d %H:%M:%S")} (#{dir}) ###"
  
  `git pull origin $(git symbolic-ref HEAD | cut -d'/' -f3)`
  `git add . -A`

Merovex

/*jslint bitwise: true, indent: 2, nomen: true, regexp: true, stupid: true*/
(function () {
  'use strict';

  var exports = {};

  exports.uuid4 = function () {
    //// return uuid of form xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx
    var uuid = '', ii;
    for (ii = 0; ii < 32; ii += 1) {

Merovex

Git Wars: GitHub vs Bitbucket

Introduction

Now, you might think the answer I'm going to give you is already obvious because I'm using GiHub right now, but it's not. Both GitHub and Bitbucket offer great Git services, but each has its own features and pricing plans. In the following... thing, I'm going to compare the two and then offer a final solution that should work for most people.

TL;DR: Both. Use GitHub for open source and public repos (you'll spend most of your time here) and Bitbucket for private repos. But, sign up for GitHub first, then import account into Bitbucket. Also, check comments for updates. P.S. I personally prefer GitHub.

Interface and Functionality

Merovex

#!/path/to/bin/ruby

Encoding.default_external = Encoding::UTF_8 # Stops LaunchD from carping
Encoding.default_internal = Encoding::UTF_8 # Ditto
require 'rubygems'
require 'json'
require 'date'
require "pathname"
require "erb"
require "yaml"