| #!/Usr/bin/env ruby | |
| require 'mail' | |
| require 'fileutils' | |
| # Check if a command line argument is provided | |
| if ARGV.length < 1 | |
| puts "Usage: ruby send_to-kindle.rb <directory containing epub files>" | |
| exit 1 |
| ruby '2.7.1' | |
| gem 'rails', github: 'rails/rails' | |
| gem 'tzinfo-data', '>= 1.2016.7' # Don't rely on OSX/Linux timezone data | |
| # Action Text | |
| gem 'actiontext', github: 'basecamp/actiontext', ref: 'okra' | |
| gem 'okra', github: 'basecamp/okra' | |
| # Drivers |
| ruby '2.7.1' | |
| gem 'rails', github: 'rails/rails' | |
| gem 'tzinfo-data', '>= 1.2016.7' # Don't rely on OSX/Linux timezone data | |
| # Action Text | |
| gem 'actiontext', github: 'basecamp/actiontext', ref: 'okra' | |
| gem 'okra', github: 'basecamp/okra' | |
| # Drivers |
| CREATE TABLE `states` ( | |
| `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, | |
| `name` varchar(191) COLLATE utf8mb4_unicode_ci NOT NULL, | |
| `code` varchar(191) COLLATE utf8mb4_unicode_ci NOT NULL, | |
| `created_at` timestamp NULL DEFAULT NULL, | |
| `updated_at` timestamp NULL DEFAULT NULL, | |
| PRIMARY KEY (`id`) | |
| ) ENGINE=InnoDB AUTO_INCREMENT=53 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; | |
| 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()}** `; |
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.
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:
| version: 2 | |
| jobs: | |
| build: | |
| docker: | |
| - image: paperist/alpine-texlive-ja | |
| steps: | |
| - run: | |
| name: Installing dependancies | |
| command: | | |
| apk add --update git patch curl |
| /*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) { |
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.