Inspired by dannyfritz/commit-message-emoji
See also gitmoji.
Commit type | Emoji |
---|---|
Initial commit | 🎉 :tada: |
Version tag | 🔖 :bookmark: |
New feature | ✨ :sparkles: |
Bugfix | 🐛 :bug: |
Inspired by dannyfritz/commit-message-emoji
See also gitmoji.
Commit type | Emoji |
---|---|
Initial commit | 🎉 :tada: |
Version tag | 🔖 :bookmark: |
New feature | ✨ :sparkles: |
Bugfix | 🐛 :bug: |
#Users
{
id: integer
username: string
email: string
created_at: datetime(iso 8601)
updated_at: datetime(iso 8601)
}
So, are you building microservices? Take a look at a few of these symptoms, and decide for yourself:
# Aliases for common git commands. E.g., enter "git d" for "git diff" | |
# These settings live in the ~/.gitconfig file. | |
[alias] | |
b = branch | |
ba = branch -a | |
ci = commit | |
co = checkout | |
d = diff | |
dc = diff --cached |
# Reset Jetbrains 2020 Products | |
import glob | |
import os | |
import winreg | |
from os import path | |
from os.path import expanduser | |
home = expanduser("~") | |
newJetbrainsHome = path.join(home, "AppData\Roaming\JetBrains") |
Consider a software that is customized for each client. It contains common components, modules, and | |
client-specific customizations thereof. For instance, | |
Common | |
+ Common.ClientA | |
+ Common.ClientB | |
ModuleA | |
+ ModuleA.ClientB | |
ModuleB | |
+ ModuleB.ClientA |
<?php | |
// -- Only one caveat : The results must be ordered so that an item's parent will be processed first. | |
// -- Simulate a DB result | |
$results = array(); | |
$results[] = array('id' => 'a', 'parent' => '', 'name' => 'Johnny'); | |
$results[] = array('id' => 'b', 'parent' => 'a', 'name' => 'Bobby'); | |
$results[] = array('id' => 'c', 'parent' => 'b', 'name' => 'Marky'); | |
$results[] = array('id' => 'd', 'parent' => 'a', 'name' => 'Ricky'); |
image: atlassian/default-image:2 | |
definitions: | |
services: | |
redis: | |
image: redis:3.2 | |
memory: 512 | |
mysql: | |
image: mysql:5.7 | |
environment: |