I hereby claim:
- I am forktheweb on github.
- I am chrhogan (https://keybase.io/chrhogan) on keybase.
- I have a public key whose fingerprint is 4384 AEEB 0630 2C07 9959 A99E 00D5 E484 668B 396E
To claim this, I am signing this object:
<template> | |
<require from="./dynamic-expression-binding-behavior"></require> | |
<require from="./debug"></require> | |
<label> | |
Address 1: | |
<input value.bind="model & dynamicExpression:'address.address1'"> | |
</label> | |
<label> | |
Address 2: |
'use strict'; | |
var path = require('path'); | |
var gulp = require('gulp'); | |
var conf = require('./conf'); | |
var browserSync = require('browser-sync'); | |
var $ = require('gulp-load-plugins')(); |
May 12 03:38:00 <sztanpet> oh no, they dont cross-compile for all archs by default, they just append the arch to everything by default | |
May 12 03:38:27 <disruptive> I'm starting to think, can't I take an SPA app written in angular2/aurelia and just run it as a standalone on something like gorilla as a router using a goat api | |
May 12 03:38:44 <disruptive> or would I need to build in chromev8 into the package too | |
May 12 03:38:48 <sztanpet> not enough buzzwords yet | |
May 12 03:38:49 <disruptive> to run it as an app | |
May 12 03:38:49 <noethics> ? | |
May 12 03:38:55 <noethics> what's that even mean | |
May 12 03:39:06 <disruptive> run a web app as an actual app | |
May 12 03:39:14 <noethics> like, as a desktop app? | |
May 12 03:39:31 <noethics> you're way better off.. not using go for that |
ssh-gitway: | |
image: segfly/ssh-gitway | |
cap_drop: | |
- ALL | |
cap_add: | |
- SYS_CHROOT | |
- SETGID | |
- SETUID | |
- CHOWN | |
volumes: |
I hereby claim:
To claim this, I am signing this object:
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j
#msgs_scroller_div::-webkit-scrollbar-track, #client_body::before, .client_container, | |
#search_terms, #client_body, #footer, ts-message, .channel_header, ts-jumper ts-jumper-container, | |
ts-jumper input[type="text"], | |
.supports_custom_scrollbar:not(.slim_scrollbar) #col_channels:hover #channels_scroller::-webkit-scrollbar-track, | |
.feature_sli_file_search #search_results.all, .feature_sli_file_search #search_results.messages, | |
.feature_sli_file_search #search_results.files{ | |
background: #333 !important; | |
} |
// TODO add colors | |
sample = { | |
"language": { | |
"backend": "node.js", | |
"middleware": "node.js", | |
"frontend": "es2018" | |
}, | |
"cloud-storage": { | |
"block": { |
query FSDL { | |
expect_behavior_connection(where: {business_requirement: {_eq: "auth.basic"}}) { | |
edges { | |
node { | |
id | |
behavior_requirement { | |
shortname | |
title | |
} | |
for_reason |